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

Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2018/04/06 11:43:00 UTC

[jira] [Updated] (IGNITE-7371) MVCC TX Repeatable read semantic

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

Igor Seliverstov updated IGNITE-7371:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> MVCC TX Repeatable read semantic
> --------------------------------
>
>                 Key: IGNITE-7371
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7371
>             Project: Ignite
>          Issue Type: New Feature
>          Components: cache
>            Reporter: Igor Seliverstov
>            Priority: Major
>             Fix For: 2.6
>
>
> Repeatable read isolation implies that each GET operation whithin tx gets a last commited version of entry *at the time the tx was started*. Curentrly we get a last commited version of entry *at the time the first read operation invokes on a particular key whithin tx.* We need to fix this unconsistence.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)