Re: read through cache refresh

2018-05-17 Thread Andrey Mashenkov
Hi,

When your data in back store has been changed, you should clear cache to
force ignite forget outdated data.
Yes cache.clear() will be enough.
If you find this method slow and you have a large dataset, then you can try
to destroy and recreate a cache instead.


Cache will not blocked during cache.clear() operation.
You should use either external lock or try to recreate cache.

On Thu, May 17, 2018 at 6:47 AM, yonggu.lee 
wrote:

> I have an ignite cache with hbase read-through. Data is fully reconstructed
> on a daily basis on the underlying hbase table.
>
> My question is, when the hbase table is totally changed, calling
> cache.clear() is enough to get the latest data?
>
> And, during processing cache.clear(), all reads to the cache will be
> blocked? I mean, the cache is locked?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>



-- 
Best regards,
Andrey V. Mashenkov


read through cache refresh

2018-05-16 Thread yonggu.lee
I have an ignite cache with hbase read-through. Data is fully reconstructed
on a daily basis on the underlying hbase table.

My question is, when the hbase table is totally changed, calling
cache.clear() is enough to get the latest data? 

And, during processing cache.clear(), all reads to the cache will be
blocked? I mean, the cache is locked?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/