You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2015/03/28 01:15:52 UTC
[jira] [Reopened] (LUCENE-6303) CachingWrapperFilter ->
CachingWrapperQuery
[ https://issues.apache.org/jira/browse/LUCENE-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand reopened LUCENE-6303:
----------------------------------
Reopen: This change triggered issues with tests that modify queries in-place after they have been put into the cache. There have been some attempts to fix it (see LUCENE-6369) but there doesn't seem to be any quick path to a fix so we should disable automatic caching for now.
> 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
> Fix For: Trunk, 5.1
>
> Attachments: LUCENE-6303.patch
>
>
> 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