[IGNITE-19497] Sql. Switch to SqlSchemaManager implementation on top of CatalogService

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Component/s: sql
• Labels: ignite-3
• Epic Link: Catalog Service
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Andrey Mashenkov
• Reporter: Andrey Mashenkov
• Created: 17/May/23 09:56
• Updated: 04/Sep/24 16:10
• Resolved: 18/Aug/23 09:10

Description

Let's switch to a new SqlSchemaManager from IGNITE-19496, which uses Catalog events, and drop old implementation.

Note: Some tests may fails due to changed guarantees and related ticked incompletion. So, let's do this in a separate feature branch.

Issue Links

• is blocked by: IGNITE-20105 Fix the bug in CatalogUtils#fromParams(ColumnParams)
• is blocked by: IGNITE-20192 Fix default length for variable-length columns.
• is blocked by: IGNITE-19496 Sql. Implement SqlSchemaManager on top of CatalogService
• is blocked by: IGNITE-20167 Query execution flow refactoring for proper using catalog version.
• Is contained by: IGNITE-19752 Ignite 3.0: Umbrella. Migrate Ignite 3 components to using Catalog
• is related to: IGNITE-17694 Hardcoded schemas in SqlQueryProcessor.
• links to: GitHub Pull Request #2441