Mirko, This query should work. Could you provide more details of what exactly you are doing (code snippet of how you execute the query, partitioned or replicated cache is used). Also I think the stack trace you've posted is missing cause, which is important to understand roots of this issue.
Sergi 2015-07-30 21:10 GMT+03:00 Mirko Raner <[email protected]>: > We need to perform some SqlQueries that use the "IN" operator to test > membership in a set, i.e. WHERE name IN ("Alice", "Bob", "Carl"). > Unfortunately, this generally seems to result in an exception: > > javax.cache.CacheException: Failed to run reduce query locally. > at > > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:553) > at > > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:777) > at > > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:59) > at > > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:811) > at > > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:59) > at > > org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:71) > > Is there a special trick as to how to initialize the query arguments, or is > this generally not supported? > If this is indeed supported, can someone point me to a working example? > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/SQL-IN-Operator-tp779.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
