You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2023/01/23 13:25:00 UTC
[jira] [Assigned] (IGNITE-18086) Add index building in IncomingSnapshotCopier
[ https://issues.apache.org/jira/browse/IGNITE-18086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko reassigned IGNITE-18086:
----------------------------------------
Assignee: Kirill Tkalenko
> 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
>
>
> 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)