ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@gridgain.com>
Subject Re: The result of cross-cache SQL joins is incomplete.
Date Mon, 02 Nov 2015 10:52:50 GMT
iceguo and Deniss

I think Denis provided slightly incorrect code snippet to work with async.

One should use varable to work with async like this:
IgniteCache asyncCache = cache.withAsync();
asyncCache.put(...);
....
asyncCache.future().get();

Denis, take a look.


On Mon, Nov 2, 2015 at 4:40 PM, Denis Magda <dmagda@gridgain.com> wrote:

> > There is another question, when I put table data into REPLICATED cache,
> This operation is synchronous or asynchronous?
>
> cache.put is synchronous. However, you can make behave him asynchronously
> this way: cache.withAsync().put(...)
>
> > If it is asynchronous, how can I know when this operation has finished?
>
> cache.withAsync().put(...);
>
> // blocks until the put above is finished
> cache.future().get();
>
>
> In addition I would like to let you know that you always can change the way
> data is synchronized during put or other modification operations using
> CacheWriteSynchronizationMode that can be changed for a CacheConfiguration.
>
> Regards,
> Denis
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/The-result-of-cross-cache-SQL-joins-is-incomplete-tp1723p1808.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Mime
View raw message