[IGNITE-19768] Port configured tables workaround from configuration to Catalog

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Catalog Service
• Assignee: Andrey Mashenkov
• Reporter: Roman Puchkovskiy
• Created: 19/Jun/23 06:53
• Updated: 04/Sep/24 16:10
• Resolved: 22/Sep/23 09:36

Description

Currently, TableManager contains a workaround (for a problem of getting of the most recent schemas without a proper Schema Sync mechanism), it works like this: on each attempt to resolve a table by ID, we look into the configuration to make sure that the table with this ID is created and not dropped yet. Also, we look into the configuration on each attempt to get a list of all tables.

A switch from Configuration to the Catalog is under way, so we need to switch this workaround from Configuration to the Catalog as well. ConfiguredTablesCache needs to be modified to achieve this.

An alternative would to be implement both the switch from Configuration to Catalog AND introduction of the proper Schema Sync at once, but this will greatly complicate the matters, it seems to be better to do these changes one after another (first Catalog, then Schema Sync).

Issue Links

• duplicates: IGNITE-19502 Separate component to keep database schema and manage changes in it
• Is contained by: IGNITE-19752 Ignite 3.0: Umbrella. Migrate Ignite 3 components to using Catalog
• links to: GitHub Pull Request #2518