[
https://issues.apache.org/jira/browse/IGNITE-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677934#comment-16677934
]
Ivan Pavlukhin commented on IGNITE-7955:
----------------------------------------
A peek operation for MVCC caches is implemented as read operation with a
special snapshot which sees all committed versions (coordinator and counter are
set to maximum, empty active transactions list). It allows retrieving latest
committed version for any key.
Useful detail: _operation counter_ component in mvcc version might contain hint
bits allowing to know that version was committed without asking TxLog.
> MVCC TX: cache peek for key-value API
> -------------------------------------
>
> Key: IGNITE-7955
> URL: https://issues.apache.org/jira/browse/IGNITE-7955
> Project: Ignite
> Issue Type: Task
> Components: cache, mvcc
> Reporter: Alexander Paschenko
> Assignee: Ivan Pavlukhin
> Priority: Major
> Fix For: 2.8
>
>
> We need to implement MVCC-compatible cache peek operation for key-value API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
