Kirill Tkalenko created IGNITE-20886:
----------------------------------------
Summary: Don't unregister indexes on CatalogEvent#INDEX_DROP
Key: IGNITE-20886
URL: https://issues.apache.org/jira/browse/IGNITE-20886
Project: Ignite
Issue Type: Improvement
Reporter: Kirill Tkalenko
At the moment, when performing an UpdateOperation, we use only those indexes
that are current at the time of the operation, which is not correct.
We must update all available indexes since the catalog version on which the
transaction began, as well as all registered indexes since the beginning of the
transaction that have not been deleted.
In this ticket, we need not unregister indexes on
*org.apache.ignite.internal.catalog.events.CatalogEvent#INDEX_DROP*
(*org.apache.ignite.internal.index.IndexManager#onIndexDrop*), since they may
be needed when performing the operations described above.
Unregistration of indexes must occur in IGNITE-20121(or IGNITE-20120) before we
realize that we no longer need the index and we can safely physically delete
this index both from the catalog (from previous versions) and its storage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
