[
https://issues.apache.org/jira/browse/IGNITE-21560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-21560:
-------------------------------------
Fix Version/s: 3.0.0-beta2
> Add schema sync before apply BuildIndexCommand
> ----------------------------------------------
>
> Key: IGNITE-21560
> URL: https://issues.apache.org/jira/browse/IGNITE-21560
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Now, before applying the
> *org.apache.ignite.internal.table.distributed.command.BuildIndexCommand* in
> *org.apache.ignite.internal.table.distributed.raft.PartitionListener#handleBuildIndexCommand*,
> we wait for the index to appear through the internal mechanism, and it is
> enough to reuse the existing schema synchronization and inherit from the
> *org.apache.ignite.internal.table.distributed.command.CatalogVersionAware*
> and pass into it catalog version in which the index get the
> *org.apache.ignite.internal.catalog.descriptors.CatalogIndexStatus#BUILDING*.
> Also, I think we will need to skip the *BuildIndexCommand* if the index has
> been removed from the catalog at the time the command is applied.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
