Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 17 Aug 2016 11:23:20 +0000 (UTC)
From: "Semen Boikov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12993274.1469722074000.328384.1471433000694@Atlassian.JIRA>
In-Reply-To: <JIRA.12993274.1469722074000@Atlassian.JIRA>
References: <JIRA.12993274.1469722074000@Atlassian.JIRA> <JIRA.12993274.1469722074517@arcas>
Subject: [jira] [Updated] (IGNITE-3601) Read-only optimistic transaction
 shouldn't throw an exception if entry version was not changed.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 17 Aug 2016 11:23:22 -0000


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

Semen Boikov updated IGNITE-3601:
---------------------------------
    Assignee:     (was: Semen Boikov)

> 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
>             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)