See my comments below. Unfortunately, that doesn't add much more detail to what exactly failed > here... >
Since it says that map query failed on node 4d469cd1-1448-4f4e-a1bc-65f1d746a504 you need to check logs on that node. I think there exception should be more informative. > 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. If I don't know steps to reproduce the issue, I can't help you. I suggest you to write a simple artificial test reproducing the problem, it will save us lots of time. Most probably IN operator works correctly but you do something wrong. > Is it OK to pass the set > parameter of the query as a java.util.Set? Again, I'm not sure what do you mean by that. How the query looks like? How do you set query arguments? > 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? > > You can look at GridCacheCrossCacheQuerySelfTest, I modified some existing there queries to check if IN operator works correctly and it does. The problem is most probably in incorrect usage. Sergi > > > > -- > 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. >
