[
https://issues.apache.org/jira/browse/IGNITE-19798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-19798:
-------------------------------------
Description:
To switch the *IndexManager* to catalog events, I need:
* receive in
*org.apache.ignite.internal.catalog.events.DropIndexEventParameters* the table
ID from which the index will need to be removed;
* atomically create the primary key index when creating a table in the catalog,
in order to avoid dependence on the creation of the primary key index waiting
for an event from the *TableManager*;
*
was:
To switch the *IndexManager* to catalog events, I need:
* receive in
*org.apache.ignite.internal.catalog.events.DropIndexEventParameters* the table
ID from which the index will need to be removed;
*
> Add functionality to the catalog to switch the IndexManager to catalog events
> -----------------------------------------------------------------------------
>
> Key: IGNITE-19798
> URL: https://issues.apache.org/jira/browse/IGNITE-19798
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> To switch the *IndexManager* to catalog events, I need:
> * receive in
> *org.apache.ignite.internal.catalog.events.DropIndexEventParameters* the
> table ID from which the index will need to be removed;
> * atomically create the primary key index when creating a table in the
> catalog, in order to avoid dependence on the creation of the primary key
> index waiting for an event from the *TableManager*;
> *
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
