[
https://issues.apache.org/jira/browse/IGNITE-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-7764:
-------------------------------------
Description:
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.
was: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.
> 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: Igor Seliverstov
> 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)
