You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2024/01/23 07:20:00 UTC

[jira] [Assigned] (IGNITE-20495) Sql. Provide IgniteTableModify with source id

     [ https://issues.apache.org/jira/browse/IGNITE-20495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Zhuravkov reassigned IGNITE-20495:
-----------------------------------------

    Assignee: Maksim Zhuravkov

> Sql. Provide IgniteTableModify with source id 
> ----------------------------------------------
>
>                 Key: IGNITE-20495
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20495
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Maksim Zhuravkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, IgniteTableModify doesn't implement interface SourceAwareIgniteRel, and, as a result, is not being assigned its own source id, although requires to be mapped on particular set of nodes with regards to the distribution of the table it modifies.
> To fully integrate TableModify into mapping process, let's make it implement SourceAwareIgniteRel. This id should be used during mapping phase to create colocation group properly, and inside execution to acquire assignments. See usages of {{UpdatableTableImpl#MODIFY_NODE_SOURCE_ID}} to find all places that should be changed. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)