You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Seliverstov (Jira)" <ji...@apache.org> on 2020/02/18 12:13:00 UTC

[jira] [Commented] (IGNITE-12692) Calcite integration. DML. Skip reducer optimization.

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

Igor Seliverstov commented on IGNITE-12692:
-------------------------------------------

UPD seems it's more efficient and natural to request from a modify node underlying table distribution and add a single distributed SUM aggregation node before it - this way a planner will try to collocate modification and source select.

Adding a single distributed table modify to search scope as an alternative will cover a case when collecting phase required.

This way we'll get desired behavior automatically.

> Calcite integration. DML. Skip reducer optimization.
> ----------------------------------------------------
>
>                 Key: IGNITE-12692
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12692
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Igor Seliverstov
>            Priority: Major
>
> Having plan tree we easily can check whether a final modification may be executed on data nodes directly or not. We should implement such kind of optimization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)