[
https://issues.apache.org/jira/browse/IGNITE-19500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-19500:
-------------------------------------
Description:
As of now, IndexManager listens configuration events to create internal
structures.
Let's make IndexManager listens CatalogService events instead.
Note: Some tests may fails due to changed guarantees and related ticked
incompletion. So, let's do this in a separate feature branch.
*Some thoughts:*
For some simplification of the transition to the catalog, I thought that adding
a table ID from the configuration and this ID when executing an catalog event
to delete a table can help us.
was:
As of now, IndexManager listens configuration events to create internal
structures.
Let's make IndexManager listens CatalogService events instead.
Note: Some tests may fails due to changed guarantees and related ticked
incompletion. So, let's do this in a separate feature branch.
> IndexManager should listen CatalogService events instead of configuration
> -------------------------------------------------------------------------
>
> Key: IGNITE-19500
> URL: https://issues.apache.org/jira/browse/IGNITE-19500
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As of now, IndexManager listens configuration events to create internal
> structures.
> Let's make IndexManager listens CatalogService events instead.
> Note: Some tests may fails due to changed guarantees and related ticked
> incompletion. So, let's do this in a separate feature branch.
> *Some thoughts:*
> For some simplification of the transition to the catalog, I thought that
> adding a table ID from the configuration and this ID when executing an
> catalog event to delete a table can help us.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
