Hi, It's expected behaviour. If a query is executed over a PARTITIONED cache, then the execution flow will be the following. The query will be parsed and split into multiple map queries and a single reduce query. All the map queries are executed on all the data nodes where cache data resides. All the nodes provide result sets of local execution to the query initiator (reducer) that, in turn, will accomplish the reduce phase by properly merging provided result sets.
On Fri, Jun 2, 2017 at 2:48 PM, sandeepbellary <[email protected]> wrote: > Hi, > > > When I issue a JDBC query on collocated Data in Ignite.It seems to be > scanning all nodes instead of the node on which affinity key resides.This > seems to be working fine for Map but jdbc query is not happening in > distribuited manner.i added collacated =true also, but with no luck. > Any help is appreciated. > > Regards, > Sandeep > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Affinity-Issue-Collocate-compute-in- > Ignite-JDBC-Query-tp13338.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
