You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (JIRA)" <ji...@apache.org> on 2016/09/05 14:25:20 UTC
[jira] [Comment Edited] (IGNITE-3601) Read-only optimistic
transaction shouldn't throw an exception if entry version was not changed.
[ https://issues.apache.org/jira/browse/IGNITE-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15465117#comment-15465117 ]
Vladislav Pyatkov edited comment on IGNITE-3601 at 9/5/16 2:24 PM:
-------------------------------------------------------------------
I found incorrect behavior of the getAndPutIfAbsent method of cache in transaction. By that reason the task has not be fixed yet.
[~sboikov] could you please look it?
was (Author: v.pyatkov):
I found incorrect behavior of the getAndPutIfAbsent method of cache in transaction. By that reason the task has not be fixed yet.
> Read-only optimistic transaction shouldn't throw an exception if entry version was not changed.
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-3601
> URL: https://issues.apache.org/jira/browse/IGNITE-3601
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexei Scherbakov
> Assignee: Semen Boikov
> Fix For: 1.8
>
> Attachments: Test.java
>
>
> Concurrent read only transactions reading the same key throw unexpected IgniteTxOptimisticCheckedException.
> They shouldn't do what because entry version was not changed.
> See the reproducer in the attachment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)