[
https://issues.apache.org/jira/browse/IGNITE-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676625#comment-16676625
]
Ivan Pavlukhin edited comment on IGNITE-7955 at 11/7/18 9:48 AM:
-----------------------------------------------------------------
*OBSOLETE ASSUMPTION*
It seems that the fastest way to make {{peek}} work is to execute it like a
read-only query. Currently, we have no way to figure out what is the last
committed version locally without obtaining an MVCC snapshot.
was (Author: pavlukhin):
It seems that the fastest way to make {{peek}} work is to execute it like a
read-only query. Currently, we have no way to figure out what is the last
committed version locally without obtaining an MVCC snapshot.
> 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)
