[
https://issues.apache.org/jira/browse/IGNITE-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-19768:
---------------------------------------
Epic Link: IGNITE-19502
> Port configured tables workaround from configuration to Catalog
> ---------------------------------------------------------------
>
> Key: IGNITE-19768
> URL: https://issues.apache.org/jira/browse/IGNITE-19768
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
