Igniters,

I've been working on the task that will let the user to retrieve version related information for a particular Cache.Entry object.
All the details are here: https://issues.apache.org/jira/browse/IGNITE-946

VersionedEntry of a given Cache.Entry can be retrieved by a call to 'Cache.Entry.unwrap(VersionedEntry.class)'. I've already fully supported 'unwrap' for Cache.Entry when it is returned from:
- Cache.invoke();
- Cache.invokeAll();
- IgniteCache.randomEntry();

The following entry points are left:
- Cache.iterator();
- IgniteCache.localEntries().

However, I doubt that it makes sense to support these two last methods.
In my understanding a use case scenario of VersionedEntry is the following: the user get a VersionedEntry for a particular key(s) using Cache.invoke, keeps it and then compares with other VersionEntries for the same key retrieved later. I don't think that the user will iterate over a cache using Cache.iterator() or IgniteCache.localEntries() in order to get a version, especially in production.

What do you think? Do you see any other real life scenarios I'm missing?

--
Denis

Reply via email to