Andrey Mashenkov created IGNITE-21609:
-----------------------------------------
Summary: 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
Fix For: 3.0
As of now, we misuse VersionedValue in TableManager/IndexManager for 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)