[
https://issues.apache.org/jira/browse/IGNITE-19548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko resolved IGNITE-19548.
--------------------------------------
Resolution: Won't Do
*org.apache.ignite.internal.distributionzones.configuration.DistributionZoneConfigurationSchema#zoneId*
already uses integer identifiers, along with the
*org.apache.ignite.internal.distributionzones.configuration.DistributionZonesConfigurationSchema#globalIdCounter*.
We must use the same global identifier (with tables and indices) when switch to
a catalog.
> Switch distribution zone IDs from UUID to int
> ---------------------------------------------
>
> Key: IGNITE-19548
> URL: https://issues.apache.org/jira/browse/IGNITE-19548
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, as zones are stored as named list items in the Configuration, they
> are internally (to the configuration) identified by UUIDs. The same UUIDs are
> also used to identify zones in the whole system.
> We need to change the latter: that is, in addition to the internal IDs
> (needed only for configuration), we need to generate integer IDs and use them
> in the rest of the system to identify zones.
> For now, zone IDs should be generated using same global counter that will be
> used to generate table and index IDs.
> Internal IDs will remain until we switch from storing tables/indices/zones in
> the Configuration to storing them in the Catalog (this is out of scope of
> this task).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
