[jira] [Resolved] (IGNITE-3484) MVCC data structure for getAll operation

["Semen Boikov (JIRA)" <ji...@apache.org>]

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

Semen Boikov resolved IGNITE-3484.
----------------------------------
    Resolution: Fixed

In initial implementation it was decided to store all versions in the same BPlusTree, and for now cleanup of unneeded versions is done by threads executing updates. Merged in ignite-3478.

> MVCC data structure for getAll operation
> ----------------------------------------
>
>                 Key: IGNITE-3484
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3484
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Alexey Goncharuk
>            Assignee: Semen Boikov
>
> 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



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)