Romain,
If it's implemented this way for now it doesn't mean that we can't
enhance the API for other use cases ;)
As I said presently it's supported for limited number of methods mostly
by performance reasons.
Please go ahead and try invoke/invokeAll and if it doesn't work fine for
you we can keep discussing what to do next.
Regards,
Denis
On 12/16/2015 1:53 PM, Romain Gilles wrote:
Hi Denis,
Thanks for you replay. And sorry to not double check it before. I see that
if I want to work with CacheEntry, I need to use the invoke method in order
to return the CacheEntry. This is the way I should do it. It sounds like
complicated for "just" getting an entry. But if you say this is the way I
will do it like that. I was just think that it could be a common use case
and therefore provide it as a shortcut.
Thanks,
Romain.
Le mer. 16 déc. 2015 à 11:34, Denis Magda <[email protected]> a écrit :
Hi Romain,
As the current documentation of org.apache.ignite.cache.CacheEntry
states it's possible to get a reference to CacheEntry and its version
only for methods that are executed over local data set stored on a node.
Among such methods are invoke & invokeAll and randomEntry.
You probably can get a CacheEntry and its non null version when a cache
iterator is in use but the version will be 'null', as far as I remember,
for those entries that are loaded from remote nodes.
Presently Ignite doesn't transfer the version from remote nodes as a
part of response by perform reasons.
Please elaborate more on your particular use case and what API you would
like to add in order to support it.
--
Denis
On 12/16/2015 12:58 PM, Romain Gilles wrote:
Hi Igniters,
I'm looking for a way to get access to the Ignite CacheEntry. For now
this
is the ways I found:
- Through the queris
- Through jsr 107 Cache Iterable
- Through jsr 107 Cache itterator
- Through IgniteCache::randomEntry()
If I remember correctly it was possible to get the CacheEntry from a
given
key in old version of gridgain community
version: GridCacheProjection::entry(K key) GridCacheEntry<K,V>
I think it could be a good to introduce this feature at IgniteCache
level.
Or maybe there is an other way to do it.
Thanks,
Romain.
