[jira] [Updated] (IGNITE-20957) Rework local partitions versioned value in table manager

["Mirza Aliev (Jira)" <ji...@apache.org>]

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

Mirza Aliev updated IGNITE-20957:
---------------------------------
    Summary: Rework local partitions versioned value in table manager  (was: Get rid of or rework local partitions versioned value in table manager)

> Rework local partitions versioned value in table manager
> --------------------------------------------------------
>
>                 Key: IGNITE-20957
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20957
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> This versioned value ( {{TableManager#localPartsByTableIdVv}} ) is currently used not correctly. It stores the map of local partition storages (table id to partition set), which are created before the partitions start. The partitions start happens on table creation and on assignment change. In first case. this VV is updated via {{VersionedValue#update}} , in the second - the partition set is supposed to be modified within one version (which is incorrect - the value corresponding to a version must be immutable).
> The only point to have this versioned value is to register indexes in the index manager when the partition storages are ready. After IGNITE-19712 there should be no such dependency (indexes may be registered in the storages as they are created), or it should look different: the assignments listener modifying indexes should wait for meta storage revision update on storages versioned value.



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