[jira] [Assigned] (IGNITE-21609) Avoid using versioned values for non-versioned objects

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

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

Andrey Mashenkov reassigned IGNITE-21609:
-----------------------------------------

    Assignee: Andrey Mashenkov

> Avoid using versioned values for non-versioned objects
> ------------------------------------------------------
>
>                 Key: IGNITE-21609
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21609
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0
>
>
> As of now, TableManager/IndexManager misuses VersionedValue while holding non-versioned objects, e.g. table instances, partitions, assignments and etc.
> Actually, we need
> 1. the latest value, but not a history, which is size of 10 entries by default. 
> 2. a future for synchronization purposes with ongoing metastorage operation.
> Also, VV requires a metastorage token for update.
> Local operations, like table/index destruction, do NOT have any token and are executed out of metastorage context, because such operations should block metastorage and further metadata elovution.



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