[
https://issues.apache.org/jira/browse/LUCENE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868630#action_12868630
]
Yonik Seeley commented on LUCENE-2468:
--------------------------------------
bq, I would lean towards letting the caches share the filter in these cases,
and advertising in these classes javadocs that this will happen. Thoughts?
I think that's prob OK - users won't notice when using filters to search, but
may get different behavior if they use it for other purposes.
Shay, as far as CachingWrapperFilter and CacheEvictionListener, it seems more
powerful to just let apps create a new query type themselves? That's the nice
part of lucene's openness to user query types - start with the code for
CachingWrapperFilter and hook up your own caching logic.
> reopen on NRT reader should share readers w/ unchanged segments
> ---------------------------------------------------------------
>
> Key: LUCENE-2468
> URL: https://issues.apache.org/jira/browse/LUCENE-2468
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Yonik Seeley
> Assignee: Michael McCandless
> Attachments: LUCENE-2468.patch
>
>
> A repoen on an NRT reader doesn't seem to share readers for those segments
> that are unchanged.
> http://search.lucidimagination.com/search/document/9f0335d480d2e637/nrt_and_caching_based_on_indexreader
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
