Hi Val, I agree with you.
Controlling query execution plan as per query is useful in this case. collocation = true does not make sense for queries without join though caches are collocated. what do you say ? i feel query executor must be intelligent enough to use collection as per query. Thanks. On 22 February 2017 at 06:09, vkulichenko <[email protected]> wrote: > Anil, > > OK, so you're talking about setting collocated flag on per query level in > JDBC driver, right? This makes sense, but it seems to be a limitation of > JDBC API rather than Ignite implementation. How would you provide a > parameter when creating a statement and/or executing a query? Do you have > any ideas how to do this? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/NOT-IN-in-ignite-tp9861p10777.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
