[
https://issues.apache.org/jira/browse/IGNITE-20293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-20293.
--------------------------------------
Resolution: Not A Problem
Not a problem since the catalog version is incremented when receiving a
response from the metastore, and it will not deploy watches until all
components have started.
> Deal with CatalogService#latestCatalogVersion at the start of the components
> ----------------------------------------------------------------------------
>
> Key: IGNITE-20293
> URL: https://issues.apache.org/jira/browse/IGNITE-20293
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
>
> At the moment, in some components, we have started using
> *org.apache.ignite.internal.catalog.CatalogService#latestCatalogVersion* so
> that we can get the latest state of the catalog after it is recovered.
> But this value is not immutable, so there may be consequences because of
> this, we need to figure it out.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
