You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2018/07/24 09:41:00 UTC

[jira] [Assigned] (IGNITE-7764) MVCC TX: Locking protocol for Key-Value API

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

Igor Seliverstov reassigned IGNITE-7764:
----------------------------------------

    Assignee: Igor Seliverstov

> MVCC TX: Locking protocol for Key-Value API
> -------------------------------------------
>
>                 Key: IGNITE-7764
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7764
>             Project: Ignite
>          Issue Type: New Feature
>          Components: sql
>            Reporter: Roman Kondakov
>            Assignee: Igor Seliverstov
>            Priority: Major
>              Labels: mvcc, sql
>
> 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.



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