Re: Cache read through with expiry policy

[o4oxide]

Hello Val,

Sorry I got it wrong on how expiry works with the cache store. I had thought
it will call a delete to remove it from the store when it expires. I just
realized that is not the case so an expiry only removes from cache not from
cache store.

Thanks for the good job.

Best Regards,



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cache-read-through-with-expiry-policy-tp2521p8222.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache read through with expiry policy

[o4oxide]

Hi vkulichenko,

This is still open and I also noticed it affects write through and write
behind as well.

Could you advise of a work around for now as I really need this feature.

Thanks



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cache-read-through-with-expiry-policy-tp2521p8199.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Cache read through with expiry policy

[kevin]

It seems that a read through does not set off an expiry policy.

eg.
cache = cache.withExpiryPolicy(new TouchedExpiryPolicy(new
Duration(TimeUnit.SECONDS, 1)))

cache.get(x) // triggers read through but this doesn't expire
cache.get(x) // do "get" again. this will trigger expiry

Can someone tell me if this is intended or not?

Thanks




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cache-read-through-with-expiry-policy-tp2521.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.