RE: Eviction Policy on Dirty data

2018-09-09 Thread Stanislav Lukyanov
With writeThrough an entry in the cache will never be "dirty" in that sense - cache store will update the backing DB at the same time the cache update happens. From: monstereo Sent: 14 августа 2018 г. 22:39 To: user@ignite.apache.org Subject: Re: Eviction Policy on Dirty data

Re: Eviction Policy on Dirty data

2018-08-14 Thread monstereo
yes, using cachestore and write through dkarachentsev wrote > Hi, > > Could you please explain how do you update database? Do you use CacheStore > with writeThrough or manually save? > > Anyway, you can update data with custom eviction policy: > cache.withExpiryPolicy(policy) [1] > > [1] >

Re: Eviction Policy on Dirty data

2018-08-14 Thread dkarachentsev
Hi, Could you please explain how do you update database? Do you use CacheStore with writeThrough or manually save? Anyway, you can update data with custom eviction policy: cache.withExpiryPolicy(policy) [1] [1]

Eviction Policy on Dirty data

2018-08-14 Thread monstereo
Let's say, I have cache in ignite. And one data is dirty(I mean, i have to upload correspond database for this data) Before updating, let's say I added one element to the cache and eviction policy occured(and dirty data will be removed). is there any mechanism to prevent eviction of dirty data