ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taras Ledkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10559) MVCC TX: Use extracted partitions to reduce target nodes for Query Update
Date Mon, 21 Jan 2019 15:11:00 GMT

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

Taras Ledkov commented on IGNITE-10559:
---------------------------------------

[~gvvinblade] I agree that explicit partition info may be reduced (use intersection) or validated
(print warning) by partition info calculated from query.
[~vozerov], what do you thing about it? What behavior must be default? Should we add new property
to choose behavior?

> MVCC TX: Use extracted partitions to reduce target nodes for Query Update
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-10559
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10559
>             Project: Ignite
>          Issue Type: Task
>          Components: mvcc
>            Reporter: Igor Seliverstov
>            Assignee: Taras Ledkov
>            Priority: Minor
>              Labels: iep-24
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We may avoid "query reduce" step on update queries without sorting/grouping by simply
sending them to all data nodes and executing update operation locally. Using extracted from
SQL partitions will reduce target nodes count and save resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message