You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2025/10/15 14:29:00 UTC

[jira] [Assigned] (IGNITE-26501) Make CatalogTableDescriptor tableVersion independent on schemaVersion

     [ https://issues.apache.org/jira/browse/IGNITE-26501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Mashenkov reassigned IGNITE-26501:
-----------------------------------------

    Assignee: Andrey Mashenkov

> Make CatalogTableDescriptor tableVersion independent on schemaVersion
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-26501
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26501
>             Project: Ignite
>          Issue Type: Improvement
>          Components: catalog ai3
>            Reporter: Viacheslav Blinov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>
> Currently in CatalogTableDescriptor tableVersion() is just a shortcut from getting the latest schemaVersion. This was introduced in this commit: [https://github.com/apache/ignite-3/commit/09116a30f7b5c92e50375d5b588821d4ec1b705a]
> This seems wrong as tableVersion is used for caching purposes of CatalogTableDescriptor which has other fields not related to the schema that can be changed independently.
> Historically this was a separate conception and field but later was merged for some reason. This also created a workaround of bumping a schema version every time when tableVersion bump is necessary. The proposal is to split those concepts making them independent as they should be.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)