You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2017/01/04 16:55:58 UTC

[jira] [Commented] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions

    [ https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798722#comment-15798722 ] 

Alexei Scherbakov commented on IGNITE-4523:
-------------------------------------------

[~vozerov], I think IGNITE-4517 is more about local queries.

The main purpose of the issue is to restrict network traffic for distributed SQL queries. 

I need this functionality very urgently for one of my customers.

Also I don't like the approach with int[] arrays as arguments to Query.

In case if contiguos partitions it is much better to have something like {{PartitionSet}} with ability to define range for performance reasons.

I think it's better to fix this special case first, and when extend to IGNITE-4517.

What do you think?



> 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)