[
https://issues.apache.org/jira/browse/IGNITE-8747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512398#comment-16512398
]
Andrew Mashenkov commented on IGNITE-8747:
------------------------------------------
The issue is slightly wider.
Also update operation doesn't handle expired entries that are already in cache
(e.g. when unswap occurs).
This results in wrong remove return result and updating value of expired entry
without resetting ttl.
We should evict expired before start update operation.
> Remove\RemoveAll method should not count expired entry as removed.
> ------------------------------------------------------------------
>
> Key: IGNITE-8747
> URL: https://issues.apache.org/jira/browse/IGNITE-8747
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, tck, test-failure
> Fix For: 2.6
>
>
> We have 2 TCK 1.0 test that are passed due to we have eagerTtl=true by
> default.
> The reason is remove() return true even if an expired entry was removed.
> Seems, we have to evict expired entry from cache on remove(), but do not
> count it as removed.
> java.lang.AssertionError
> at
> org.jsr107.tck.expiry.CacheExpiryTest.expire_whenAccessed(CacheExpiryTest.java:326)
> java.lang.AssertionError: expected:<0> but was:<1> at
> org.jsr107.tck.expiry.CacheExpiryTest.testCacheStatisticsRemoveAll(CacheExpiryTest.java:160)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
