Hi Jose, You can probably use an IgniteClosure or an IgniteRunnable as you expect a return value from your compute job. An IgniteCallable may not be a good idea as it does not return a value. If you want your queries to go all nodes, a broadcast can be used. However, if you already know specific nodes on which your data resides, you might as well just use the affinityRun
Regards, RH On Fri, Jan 25, 2019 at 6:09 AM joseheitor <j...@heitorprojects.com> wrote: > Which IgniteCompute function would be best suited to this task?... > > Cluster has SQL table configured in partitioned cache (records distributed > over several nodes). > > On all nodes, I would like to asynchronously execute logic which... > > - SQL SELECT query for matching records on each node (retrieving only > records from primary, not backup cache partition) > > - process and aggregate data from each record of each local node's > recordset, and > > - return the resulting object(s) to the application > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
