[
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.
* switch TableManager, IndexManager, SqlSchemaManager, SchemaRegistry to
implementations that uses Catalog events.
* drop schema related code from configuration.
* drop outdated code from TableManager, IndexManager, SqlSchemaManager,
SchemaRegistry.
* describe Catalog flow in README.md
* make a PR for merging feature branch to main (if applicable).
was:
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.
> 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.
> * switch TableManager, IndexManager, SqlSchemaManager, SchemaRegistry to
> implementations that uses Catalog events.
> * drop schema related code from configuration.
> * drop outdated code from TableManager, IndexManager, SqlSchemaManager,
> SchemaRegistry.
> * describe Catalog flow in README.md
> * make a PR for merging feature branch to main (if applicable).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
