You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (JIRA)" <ji...@apache.org> on 2017/02/10 13:30:42 UTC

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

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

Stanilovsky Evgeny reassigned IGNITE-4484:
------------------------------------------

    Assignee: Stanilovsky Evgeny

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