[
https://issues.apache.org/jira/browse/IGNITE-19082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-19082:
--------------------------------------
Description:
Let's
* use Catalog by default as a single schema management point.
* drop IndexManager implementation.
* replace SchemaManager with Catalog.
* rewrite SchemaRegistry as a cache for storage descriptors, which, seems, are
Catalog descriptors enriched with storage specific stuff.
* drop schema related code from configuration.
* drop outdated code from TableManager.
was:
Let's
* implement CatalogManager methods that will validate and save catalog changes
to the MetaStorage.
* implement Metastorage WatchListener that will apply these changes and update
CatalogService state.
Storing catalog snapshot may be ineffective as we may need to calculate a diff
between old and new catalog version for further event triggering purpose. But
we may save a while descriptors with some meta about the operation.
Note: Let's make these changes aside to avoid breaking the current
implementation.
> Use Catalog instead of SchemaManager and cleanup dead code.
> -----------------------------------------------------------
>
> Key: IGNITE-19082
> URL: https://issues.apache.org/jira/browse/IGNITE-19082
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Let's
> * use Catalog by default as a single schema management point.
> * drop IndexManager implementation.
> * replace SchemaManager with Catalog.
> * rewrite SchemaRegistry as a cache for storage descriptors, which, seems,
> are Catalog descriptors enriched with storage specific stuff.
> * drop schema related code from configuration.
> * drop outdated code from TableManager.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
