[
https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15800616#comment-15800616
]
Vladimir Ozerov commented on IGNITE-4523:
-----------------------------------------
Alex,
IGNITE-4517 is about distributed queries of course :-) This is why I though
that this ticket is duplicate - they both aim to restrict distributed query
execution to certain partitions. As per int[]. may be array is not the best
choice. However, I also do not like partition range - it appears to be too
specific. Usually partitions are distributed in "random" fashion from user
perspective.
> 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: 2.0
>
>
> 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)
