You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/01/24 10:24:00 UTC

[jira] [Commented] (IGNITE-18086) Add index building in IncomingSnapshotCopier

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

Roman Puchkovskiy commented on IGNITE-18086:
--------------------------------------------

The patch looks good to me, thanks!

> Add index building in IncomingSnapshotCopier
> --------------------------------------------
>
>                 Key: IGNITE-18086
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18086
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> It was found that in *org.apache.ignite.internal.table.distributed.raft.snapshot.incoming.IncomingSnapshotCopier* there is no logic related to rebuilding indexes on a full rebalance, which is a mistake. 
> It is not yet clear exactly how to do this correctly, but it is proposed to do it as for *org.apache.ignite.internal.table.distributed.raft.PartitionListener#addToIndexes*, i.e. pass the consumer to *IncomingSnapshotCopier* which will rebuild the indexes itself.
> What you can see:
> * *org.apache.ignite.internal.table.TableImpl#indexStorageAdapters*



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