[IGNITE-19502] Separate component to keep database schema and manage changes in it

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: persistence, sql
• Labels: ignite-3
• Epic Name: Catalog Service
• Assignee: Kirill Tkalenko
• Reporter: Sergey Chugunov
• Created: 17/May/23 10:28
• Updated: 04/Sep/24 16:10
• Resolved: 22/Sep/23 10:05

Description

Right now database schema information in Ignite 3.0 is stored and treated as regular configuration. All business processes related to schema changes are distributed via  internal mechanisms of configuration engine and orchestrated ad-hoc by consumer components like TableManager or IndexManager.

But there is a strong evidence that API and guarantees of configuration engine don't satisfy important requirements that emerge in the field of db schema management.

So we need to stop treating schema as any other configuration and move it to a separate component called Catalog Service.
This component will provide high-level API to modify the schema and will take responsibility for all other necessary processes like synchronizing schema changes between nodes, managing schema change events, notifying all necessary components and providing orchestration between them.

Issue Links

• causes: IGNITE-20617 Sql. Performance degradation in SELECTS (2 nodes VS 1 node)
• fixes: IGNITE-19223 Implement accumulation of schema updates in CatalogService
• fixes: IGNITE-19224 Implement reading a table schema by a timestamp
• is duplicated by: IGNITE-19768 Port configured tables workaround from configuration to Catalog
• is duplicated by: IGNITE-19752 Ignite 3.0: Umbrella. Migrate Ignite 3 components to using Catalog
• is related to: IGNITE-19792 Support @Immutable logic for distributed configuration
• mentioned in: Page Loading...