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

Posted to dev@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/02/12 07:55:12 UTC

[jira] [Resolved] (IGNITE-92) Properly handle zero duration provided by expiry policy

     [ https://issues.apache.org/jira/browse/IGNITE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov resolved IGNITE-92.
--------------------------------
    Resolution: Fixed

> Properly handle zero duration provided by expiry policy
> -------------------------------------------------------
>
>                 Key: IGNITE-92
>                 URL: https://issues.apache.org/jira/browse/IGNITE-92
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>             Fix For: sprint-1
>
>
> If ExpiryPolicy returns zero duration (special case when Duration.isZero() is true) then entry should be immediately discarded, in current implementation zero duration is converted to minimal duration 1ms.
> This issue casues TCK failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)