[jira] [Commented] (LUCENE-6303) CachingWrapperFilter -> CachingWrapperQuery

["Robert Muir (JIRA)" <ji...@apache.org>]

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

Robert Muir commented on LUCENE-6303:
-------------------------------------

+1. about the FilterCache:

it would be nice, for example, if it worked out of box completely with simple defaults, with some way for users to configure/disable/plug in their own on indexsearcher (e.g. setCache or policy or whatever).

this would give us freedom to cache 'implicit' filters, too using the logic we already have, for example if we see the same query over and over with needsScore=false just because it was in a booleanquery prohibited clause. 



> CachingWrapperFilter -> CachingWrapperQuery
> -------------------------------------------
>
>                 Key: LUCENE-6303
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6303
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>
> As part of the filter -> query migration, we should migrate the caching wrappers (including the filter cache).
> I think the behaviour should be to delegate to the wrapped query when scores are needed and cache otherwise like CachingWrapperFilter does today.
> Also the cache should ignore query boosts so that field:value^2 and field:value^3 are considered equal if scores are not needed.



--
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