[
https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863703#comment-15863703
]
ASF GitHub Bot commented on IGNITE-4484:
----------------------------------------
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/1522
IGNITE-4484 fix not compliant with tx isolation semantics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4484
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1522.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1522
----
commit 28ad4d6d97d706c017209566977a7ca6cb033a6d
Author: Evgeny Stanilovskiy <[email protected]>
Date: 2017-02-13T13:01:25Z
IGNITE-4484 fix not compliant with tx isolation semantics
----
> Call commit for read-only transactions.
> ---------------------------------------
>
> Key: IGNITE-4484
> URL: https://issues.apache.org/jira/browse/IGNITE-4484
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 1.8
> Reporter: Alexei Scherbakov
> Assignee: Stanilovsky Evgeny
> Fix For: 1.9
>
>
> IGNITE-3601 introduces a behavior, which is not compliant with tx isolation
> semantics.
> Read-only transaction doesn't throw optimisitc exception in case if entry
> version were changes by other writing tx.
> With the appearance of IGNITE-4285 this is no longer needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
