Hi, Thanks for the reply.I understand that query will be split into a number of subqueries for final reduce in PARTITIONED CACHE, but if I issue a query for a single record(which ideally should be present in one node i.e., NON-REPLICATED cache), then the above behaviour is hampering the performance of the application.Is there any way to restrict that behaviour?
Regards, Sandeep -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-Issue-Collocate-compute-in-Ignite-JDBC-Query-tp13338p13685.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
