[
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
* ensure Catalog is used by default as a single schema management point by
TableManager, IndexManager, SqlSchemaManager, SchemaRegistry.
* -drop schema related code from configuration.-
* -drop outdated code from TableManager, IndexManager, SqlSchemaManager,
SchemaRegistry.-
* Let’s remove using/keeping schema name instead of schema id (NewIndexEntry
class as example)
was:
Let's
* ensure Catalog is used by default as a single schema management point by
TableManager, IndexManager, SqlSchemaManager, SchemaRegistry.
* drop schema related code from configuration.
* drop outdated code from TableManager, IndexManager, SqlSchemaManager,
SchemaRegistry.
* make a PR for merging feature branch to main (if applicable).
* ensure there are end-to-end tests for the cases (if applicable) described in
CatalogServiceSelfTest. Also drop InternalSchemaTest.
* Let’s remove using/keeping schema name instaed of schema id (NewIndexEntry
class as example)
> Catalog. 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: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Let's
> * ensure Catalog is used by default as a single schema management point by
> TableManager, IndexManager, SqlSchemaManager, SchemaRegistry.
> * -drop schema related code from configuration.-
> * -drop outdated code from TableManager, IndexManager, SqlSchemaManager,
> SchemaRegistry.-
> * Let’s remove using/keeping schema name instead of schema id (NewIndexEntry
> class as example)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
