[jira] [Resolved] (LUCENE-6483) Core closed listeners should be called with the same cache key as the one returned by getCoreCacheKey

["Adrien Grand (JIRA)" <ji...@apache.org>]

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

Adrien Grand resolved LUCENE-6483.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 5.2
                   Trunk

> Core closed listeners should be called with the same cache key as the one returned by getCoreCacheKey
> -----------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-6483
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6483
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>             Fix For: Trunk, 5.2
>
>         Attachments: LUCENE-6483.patch
>
>
> Core cache keys are typically used for caching, for instance we use them in the query cache and when uninverting.
> However, since FilterLeafReader delegates addCoreClosedListener by default, these listeners will always be called with the cache key of the wrapper reader. So if you happen to use a filter reader that overrides the core cache key, you are going to try to evict on a different key than the one that you used for caching.
> We should ensure that core closed listeners are always called on the same key as the one returned by #getCoreCacheKey



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org