[
https://issues.apache.org/jira/browse/IGNITE-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429067#comment-16429067
]
Denis Magda commented on IGNITE-8125:
-------------------------------------
[~sid_human], Ignite SQL engine is not PostgreSQL compliant. The engine
supports ANSI-99 syntax of H2 database that is used internally for some of the
needs: https://apacheignite-sql.readme.io/docs/how-ignite-sql-works
So, it's not an issue.
> Returns null on cache querying on column type PGOBJECT (JSONB) superset or @>
> -----------------------------------------------------------------------------
>
> Key: IGNITE-8125
> URL: https://issues.apache.org/jira/browse/IGNITE-8125
> Project: Ignite
> Issue Type: Bug
> Components: cache, jdbc, sql
> Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4
> Reporter: Siddarth sreeni
> Priority: Critical
> Labels: documentation, fix-by-workaround
>
> Apache Ignite briefly discusses the uses of SQL Cache query. It talks about
> the different transactional query it can be used to done. Apache Ignite is as
> said supported on PostGreSQL databases.
> For example: In a table of column type JSONB. Querying for a specific object
> superset in a column returns Null.
> Query: Select * from Table where column @> 'Object'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
