Description
3Currently 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.
Attachments
Issue Links
- Is contained by
-
IGNITE-4509 SQL: query with condition on affinity columns and without joins and subqueries should go to affinity node only
- Resolved
-
IGNITE-4510 SQL: co-located query may calculate target partition in advance in some cases
- Closed
- is duplicated by
-
IGNITE-4517 Add ability to execute SQL queries on certain partition(s)
- Resolved
- relates to
-
IGNITE-4378 Affinity function should support assigning partition to subset of cluster nodes
- Open
-
IGNITE-4875 Allow execution over explicit set of partitions for every non-SQL query type with data integrity guarantees.
- Open
-
IGNITE-4517 Add ability to execute SQL queries on certain partition(s)
- Resolved
- links to