You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/08/16 15:35:01 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 ]
Vladimir Ozerov updated IGNITE-7371:
------------------------------------
Component/s: mvcc
> 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, mvcc
> Reporter: Igor Seliverstov
> Priority: Major
> Fix For: 2.7
>
>
> 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)