You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Michael McCandless (Jira)" <ji...@apache.org> on 2020/05/04 15:02:00 UTC

[jira] [Commented] (LUCENE-9361) Consider removing CachingCollector

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

Michael McCandless commented on LUCENE-9361:
--------------------------------------------

Does the query cache also cache scores too now?

> Consider removing CachingCollector
> ----------------------------------
>
>                 Key: LUCENE-9361
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9361
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Major
>
> We have a caching collector implementation that is used by the grouping module to avoid running queries twice when doing two-phase grouping queries.  This stores things in a flat array of int[maxDoc], and optionally stores scores as well in a parallel float[] array.  Given that we have a much more efficient way of caching matching documents per-segment in the built-in QueryCache, should we consider removing this collector entirely and advise users to configure query caches appropriately instead?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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