[
https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820870#comment-15820870
]
Alexei Scherbakov commented on IGNITE-4523:
-------------------------------------------
Dmitriy, I briefly'll describe API changes as you asked on dev list.
I've introduced PartitionSet [1] class as a new field in Query class.
It represents random or contiguous ordered set of partitions.
Currently this field is only handled by SQL engine, other query types ignore it.
[1]
https://github.com/ascherbakoff/ignite/blob/4dcfaad50aac20370a96acbc6e6d0768b8f90b7c/modules/core/src/main/java/org/apache/ignite/cache/query/PartitionSet.java
> Allow distributed SQL query execution over explicit set of partitions
> ---------------------------------------------------------------------
>
> Key: IGNITE-4523
> URL: https://issues.apache.org/jira/browse/IGNITE-4523
> Project: Ignite
> Issue Type: Improvement
> Components: cache, SQL
> Affects Versions: 1.8
> Reporter: Alexei Scherbakov
> Assignee: Alexei Scherbakov
> Fix For: 1.9
>
>
> Currently distributed SQL query is executed on all nodes containing primary
> partitions for a cache, sending map query requests on all nodes in grid.
> Sometimes we know in advance which partitions hold a data for query, on
> example, in case of custom affinity function.
> Therefore it's possible to reduce number of nodes receiving map query request
> by providing explicit set of partitions, which will give significant
> performance advantage and traffic reduction in case of very large clusters.
> Internally we already have such functionality, so the only necessary thing is
> to provide public API for what.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
