[ https://issues.apache.org/jira/browse/IGNITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Seliverstov updated IGNITE-5937: ------------------------------------- Fix Version/s: (was: 2.5) 2.6 > Mvcc data structure for SQL queries > ----------------------------------- > > Key: IGNITE-5937 > URL: https://issues.apache.org/jira/browse/IGNITE-5937 > Project: Ignite > Issue Type: Task > Components: sql > Reporter: Semen Boikov > Assignee: Semen Boikov > Priority: Major > Fix For: 2.6 > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)