[
https://issues.apache.org/jira/browse/IGNITE-19531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-19531:
---------------------------------------
Description:
Currently, as tables 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 tables 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 tables.
For now, table IDs should be generated using same global counter that will be
used to generate index and zone 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).
> Switch table IDs from UUIDs to integers
> ---------------------------------------
>
> Key: IGNITE-19531
> URL: https://issues.apache.org/jira/browse/IGNITE-19531
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, as tables 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 tables 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 tables.
> For now, table IDs should be generated using same global counter that will be
> used to generate index and zone 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)
