Hi Shawn, For map-reduce operations is most suitable ComputeTask [1], which has map/reduce methods. In map() method you may select nodes on which start processing according to key (refer Ignite.affinity() [2,3]). Result will be reduced and returned to the client.
In summary, client invokes SQL to collect keys and runs ComputeTask`s mapped on nodes that has keys/values that should be processed (this will allow not to transfer over network big values). [1] https://ignite.apache.org/releases/1.8.0/javadoc/org/apache/ignite/compute/ComputeTask.html [2] https://ignite.apache.org/releases/1.8.0/javadoc/org/apache/ignite/Ignite.html#affinity(java.lang.String) [3] https://ignite.apache.org/releases/1.8.0/javadoc/org/apache/ignite/cache/affinity/Affinity.html -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p9967.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
