ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Mashenkov <andrey.mashen...@gmail.com>
Subject Re: How to query to local partition cache data
Date Mon, 23 Oct 2017 15:40:53 GMT

setLocal - if true then query will be executed on local data node only.
setCollocated - if true then rows are collocated on GROUP BY field and
Ignite can evaluate aggregate functions on Map step.
setDistributedJoins - if true then Ignite will try to join rows with rows
on other nodes.

Would you please clarify what and how you observe the weird things?

In first case, affinityRun makes task to be executed on node that is
primary to Key given, but local SQL query will run on all primary data on
available on local node.

In second case, using setPartition restrict SQL query with given Partition
and a Key can be non-affinity key for this partition.
So, here task can be run on node that is primary for Key=1, but make a
remote query to node that is primary to partition=1.

On Sun, Oct 22, 2017 at 11:53 AM, dark <ekdxhrl0096@gmail.com> wrote:

> Result of the document
> setLocal is a local query
> setCollocated specifies that the data associated with Cache's Join function
> is local
> It seems like this.
> But why does the Partitioned Cache increase the GridQueryExecutor's Task on
> all nodes?
> Thank you.
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Best regards,
Andrey V. Mashenkov

View raw message