Caused by:
javax.cache.CacheException: Failed to execute map query on the node:
4d469cd1-1448-4f4e-a1bc-65f1d746a504, class
org.apache.ignite.IgniteCheckedException:Failed to execute SQL query.
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:209)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:199)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:180)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:136)
at
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1608)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:690)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:58)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:653)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
Unfortunately, that doesn't add much more detail to what exactly failed
here...
I can't paste the code as it is owned by a client, but the problem seems
clearly related to the use of the IN operator. Is it OK to pass the set
parameter of the query as a java.util.Set? I couldn't find an actual example
of a SqlQuery with an IN operator. Is there maybe some test code in the
Ignite project that uses this feature and could serve as an example?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SQL-IN-Operator-tp779p799.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
