Async caches, invoke() and EntryProcessor

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Async caches, invoke() and EntryProcessor

Ognen Duzlevski
After reading this: http://apacheignite.readme.io/v1.0/docs/jcache and
knowing (from personal experience) to throw away the return values of
methods like containsKey() in a cache.withAsync() mode of operation - how
does the async mode and associated future() interplay with invoke() and a
custom EntryProcessor within which a get() method is used?

Thanks!
Ognen
Reply | Threaded
Open this post in threaded view
|

Re: Async caches, invoke() and EntryProcessor

dsetrakyan
Ognen,

I am not sure I understand the question. If async mode is enabled, the
"invoke(...)" method works the same as any other method that supports
asynchronous behavior, i.e. you would get the return value using
IgniteCache.future().get() method.

D.

On Fri, May 1, 2015 at 9:20 PM, Ognen Duzlevski <[hidden email]>
wrote:

> After reading this: http://apacheignite.readme.io/v1.0/docs/jcache and
> knowing (from personal experience) to throw away the return values of
> methods like containsKey() in a cache.withAsync() mode of operation - how
> does the async mode and associated future() interplay with invoke() and a
> custom EntryProcessor within which a get() method is used?
>
> Thanks!
> Ognen
>