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/25 13:37:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16627373#comment-16627373 ]
Andrew Mashenkov edited comment on IGNITE-7764 at 9/25/18 1:36 PM:
-------------------------------------------------------------------
[~vozerov],
# I've fixed "Contains" operations and add some tests.
# For now, we always enlist updates in given order via setting "GridNearTxEnlistFuture.sequential" flag to true.
This flag is always true for query updates as we do not know full data set at a time future has been created.
For putAll (and other batch operations) full update map is known and we can make per-node batches full filled before send,
but unordered updates can cause a deadlock and we have to discuss this optimization.
Fixed and IGNITE-9688 was created.
3 & 4.Fixed.
5. IGNITE-9689 has been created.
6. IGNITE-9690 has been created.
was (Author: amashenkov):
[~vozerov],
# I've fix "Contains" operations and add some tests.
# For now, we always enlist updates in given order via setting "GridNearTxEnlistFuture.sequential" flag to true.
This flag is always true for query updates as we do not know full data set at a time future has been created.
For putAll (and other batch operations) full update map is known and we can make per-node batches full filled before send,
but unordered updates can cause a deadlock and we have to discuss this optimization.
Fixed and IGNITE-9688 was created.
3 & 4.Fixed.
5. IGNITE-9689 has been created.
6. IGNITE-9690 has been created.
> 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)