You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/09/11 13:07:00 UTC

[jira] [Assigned] (IGNITE-7764) MVCC TX: make cache basic operations support Mvcc tx mode.

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

Andrew Mashenkov reassigned IGNITE-7764:
----------------------------------------

    Assignee: Andrew Mashenkov  (was: Igor Seliverstov)

> MVCC TX: make cache basic operations support Mvcc tx mode.
> ----------------------------------------------------------
>
>                 Key: IGNITE-7764
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7764
>             Project: Ignite
>          Issue Type: New Feature
>          Components: mvcc, sql
>            Reporter: Roman Kondakov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>             Fix For: 2.7
>
>
> We need to implement an MVCC-compatible locking protocol for Key-Value API. At the moment during transactions with KV operations if entry we are going to change is unlocked we do not check if it has been changed by the previous transaction. See IGNITE-6935.
>  
> Lets make get/getAll, put/PutAll/getAndPut, remove/removeAll/getAndRemove operations consistent with SQL queries in MVCC mode at first
> as it blocks many other tickets. Other operations can be implemented within separate tickets in parallel once this ticket will be resolved.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)