ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hagmonk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store
Date Wed, 21 Sep 2016 19:58:20 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510991#comment-15510991
] 

Hagmonk commented on IGNITE-3699:
---------------------------------

I came here and created a JIRA account just to say that this patch applies cleanly, and resolves
the issue for me. It was going to be a serious problem if my CacheStore backed cache could
not be managed with an expiry policy! I tested the patch using a CreatedExpiryPolicy and ModifiedExpiryPolicy.
I applied the patch against bcbe8cc4492449957ff983976f8f16e090c0b239.

> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --------------------------------------------------------------
>
>                 Key: IGNITE-3699
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3699
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.7
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>             Fix For: 1.8
>
>         Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be triggered on
{{get()}} operation if the entry is loaded from the store. Currently this is not happening.
> Test reproducing the issue is attached.



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

Mime
View raw message