Thanks Mihail! Thanks Denis. Our logic seem not quite straightforward. we set the expiry policy to our Cache, data more than one hour should not be kept in cache.
But meaning while if this entry with a specific attribute flag is set to true, it should never be expired. We notice Eviction policy have a Eviction filter to exclude some entry from being evicting. while expiry policy have no corresponding filter seem. Thanks for your explanation! Regards Aaron [email protected] From: Denis Magda Date: 2017-09-09 12:16 To: user Subject: Re: What's the current behaviour when we use the eviction filter + expiry plicy? Aaron, Mihail, Frankly, I didn’t get the initial question nor the suggestion. Just in case, this is the eviction policies' doc (reworked prior 2.0 release) and the expiration policies [2]. Note that the expiration is supported for entries cached in Java heap only. Please look over the docs. Probably you’ll find a correct answer there. [1] https://apacheignite.readme.io/v2.1/docs/evictions [2] https://apacheignite.readme.io/v2.1/docs/expiry-policies — Denis On Sep 8, 2017, at 11:04 AM, Mikhail <[email protected]> wrote: Hi Aaron, I don't see anything similar for expiration like for eviction. I think the easiest solution is to put that data to another cache with no expiration policy. Thanks, Mikhail. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
