[IGNITE-3484] MVCC data structure for getAll operation

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: cache, mvcc
• Assignee: Semen Boikov
• Reporter: Alexey Goncharuk
• Created: 14/Jul/16 21:32
• Updated: 16/Aug/18 15:52
• Resolved: 11/Oct/17 08:33

Description

Need implement some data structure to store/get multiple entry versions:

• committed value at first is stored in separate data structure (there also need store related tx id to filter out data for non-finished transactions), probably existing BPlusTree can be used
• periodically need flush data for finished transaction in 'main' hash index
• 'getAll' operation should include max 'visible' ID and list of active transactions, this information should be used to find last 'visible' version in 'mvcc' or 'main' index

Issue Links

• Is contained by: IGNITE-6874 MVCC: base functionality