[
https://issues.apache.org/jira/browse/IGNITE-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694486#comment-16694486
]
Ivan Pavlukhin commented on IGNITE-10167:
-----------------------------------------
[~vozerov], [~amashenkov], it looks like that it is possible to cleanup
expiration policy arguments from
{{org.apache.ignite.internal.processors.cache.GridCacheEntryEx#peek}} methods
because passed policy is always {{null}}. But as a result a lot of files will
be touched with changes not related to {{IgniteCache.localEntries}}
functionality. It will complicate the PR.
I see 2 options. First is doing cleanup refactoring in scope of this ticket.
Second is doing it in separate ticket. I can go with either of them.
> MVCC-compatible IgniteCache.localEntries
> ----------------------------------------
>
> Key: IGNITE-10167
> URL: https://issues.apache.org/jira/browse/IGNITE-10167
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Ivan Pavlukhin
> Assignee: Ivan Pavlukhin
> Priority: Major
> Fix For: 2.8
>
>
> IgniteCache API method {{localEntries}} should be supported. The idea is to
> provide an entries iterator seeing latest committed versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
