[IGNITE-16611] [Versioned Storage] Version chain data structure for RocksDB-based storage

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha5
• Component/s: persistence
• Labels: iep-74 ignite-3
• Epic Link: MV Store
• Ignite Flags: Docs Required
• Assignee: Ivan Bessonov
• Reporter: Sergey Chugunov
• Reviewer: Alexey Scherbakov
• Created: 22/Feb/22 07:53
• Updated: 04/May/22 14:32
• Resolved: 29/Apr/22 12:38

Description

To support Concurrency Control and implement effective transactions capability to store multiple values of the same key is needed in existing storage.

Version chain

Key component here is a special data structure called version chain: it is a list of all versions of a particular key, with the most recent version at the beginning (HEAD).

Each entry in the chain contains value, reference to the next entry in the list, begin and end timestamps and id of active transaction that created this version.

There are at least two approaches to implement this structure on top of RocksDB:

• Combine original key and version into a new key which is put into a RocksDB tree. In that case to restore version chain we need to iterate over the tree using original key as a prefix.
• Use original key as-is but make it pointing not to the value directly but to an array containing version and other metainformation (ts, id etc) and keys in some secondary tree.

New API to manage versions

The following new API should be implemented to provide access to version chain:

• Methods to manipulate versions: add new version to the chain, commit uncommited version, abort uncommited version.
• Method to cleanup old versions from the chain.
• Method to scan over keys up to provided timestamp.

Issue Links

• Dependency: IGNITE-16881 Integrate MV-storage into current tx implementation
• links to: GitHub Pull Request #787