You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by Denis Magda <dm...@apache.org> on 2017/04/20 23:17:01 UTC

Expiration Policy and Page Memory (Ignite 2.0)

Alex G., Igniters,

What’s a scope of expiration policy applicability in Ignite 2.0? Does it work for all the entries in the page memory or only for those that end up in the optional on-heap cache of the page memory?

—
Denis

Re: Expiration Policy and Page Memory (Ignite 2.0)

Posted by Denis Magda <dm...@apache.org>.

Excellent, thanks! Then that documentation page will be left unchanged.

—
Denis

> On Apr 21, 2017, at 8:53 AM, Alexey Goncharuk <al...@gmail.com> wrote:
> 
> Denis,
> 
> Semantically nothing changed for expiry policies, it applies for all local
> entries.
> 
> 2017-04-21 2:17 GMT+03:00 Denis Magda <dm...@apache.org>:
> 
>> Alex G., Igniters,
>> 
>> What’s a scope of expiration policy applicability in Ignite 2.0? Does it
>> work for all the entries in the page memory or only for those that end up
>> in the optional on-heap cache of the page memory?
>> 
>> —
>> Denis

Re: Expiration Policy and Page Memory (Ignite 2.0)

Posted by Alexey Goncharuk <al...@gmail.com>.

Denis,

Semantically nothing changed for expiry policies, it applies for all local
entries.

2017-04-21 2:17 GMT+03:00 Denis Magda <dm...@apache.org>:

> Alex G., Igniters,
>
> What’s a scope of expiration policy applicability in Ignite 2.0? Does it
> work for all the entries in the page memory or only for those that end up
> in the optional on-heap cache of the page memory?
>
> —
> Denis