You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/10 16:22:00 UTC

[jira] [Commented] (IGNITE-4484) Call commit for read-only transactions.

    [ https://issues.apache.org/jira/browse/IGNITE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715018#comment-16715018 ] 

ASF GitHub Bot commented on IGNITE-4484:
----------------------------------------

Github user zstan closed the pull request at:

    https://github.com/apache/ignite/pull/1522


> 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
>            Priority: Major
>             Fix For: 2.0
>
>
> 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
(v7.6.3#76005)