[IGNITE-19752] Ignite 3.0: Umbrella. Migrate Ignite 3 components to using Catalog

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.0
• Component/s: persistence, sql
• Labels: ignite-3
• Epic Link: Catalog Service
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 16/Jun/23 07:51
• Updated: 04/Sep/24 16:09
• Resolved: 22/Sep/23 10:05

Description

This umbrella ticket for refactoring of main Ignite 3 components to make them using the Catalog.
Each of tickets separately may broke some functionality and test, so let's merge them into a feature branch first.
Once feature branch will be stable, let's merge all of them to the main at once.

Issue Links

• blocks: IGNITE-18426 Sql. Fix distribution function to use the distribution zone ID instead of the table ID.
• blocks: IGNITE-19082 Catalog. Cleanup dead code.
• blocks: IGNITE-15556 Drop SchemaBuilder API.
• contains: IGNITE-19497 Sql. Switch to SqlSchemaManager implementation on top of CatalogService
• contains: IGNITE-19499 TableManager should listen CatalogService events instead of configuration
• contains: IGNITE-19500 IndexManager should listen CatalogService events instead of configuration
• contains: IGNITE-19501 SchemaManager should use CatalogService for building BinaryRow descriptors
• contains: IGNITE-19768 Port configured tables workaround from configuration to Catalog
• duplicates: IGNITE-19502 Separate component to keep database schema and manage changes in it
• is blocked by: IGNITE-19942 Mirror Configuration changes to Catalog.
• links to: catalog-feature