Alan Woodward created LUCENE-9361: ------------------------------------- Summary: 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
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-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org