[
https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-7371:
-------------------------------------
Description:
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.-
A value that just has been got, should be cached locally.
was: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.
> 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.-
> A value that just has been got, should be cached locally.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
