You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/05/30 14:04:00 UTC
[jira] [Resolved] (IGNITE-19524) Switch table and index IDs from UUIDs to integers
[ https://issues.apache.org/jira/browse/IGNITE-19524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy resolved IGNITE-19524.
----------------------------------------
Resolution: Fixed
Closing as all parts of this task are implemented
> Switch table and index IDs from UUIDs to integers
> -------------------------------------------------
>
> Key: IGNITE-19524
> URL: https://issues.apache.org/jira/browse/IGNITE-19524
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, tables' and indices' IDs are UUIDs. CatalogService is going to require them to be integers.
> Actually, tables currently already have an alternative intId generated centrally. We can do the same for main IDs and remove the intId.
> It makes sense to generate IDs of all objects (tables/indeces/distribution zones/etc) in the same namespace: that is, if there is a table with ID=123, no other object can have its ID=123.
> It's not clear yet whether the type should be int or long.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)