Description
Need implement some data structure to store/query multiple entry versions.
One possible option:
- committed value at first is stored in separate BPlusTree index (there also need store related tx id to filter out data for non-finished transactions)
- periodically flush data for finished transaction in 'main' index
- for SQL queries need merge result from main index and filtered 'mvcc' index. Note: it is possible 'mvcc' index will contain multiple committed versions of the same entry, need make sure only one last one will appear in result.
Attachments
Issue Links
- Is contained by
-
IGNITE-4191 SQL: support transactions
- Resolved
-
IGNITE-6874 MVCC: base functionality
- Closed