Thanks for the clarification Greg. I've been looking into this recently and
filed https://issues.apache.org/jira/browse/LUCENE-9938 based on a hunch
that these DocIdSetIterator.all(maxDoc) iterators have a
non-negligible cost inside ConjunctionDISI. Ultimately I closed the issue
because the TPI
Just chiming in here to answer David's question since I have some familiarity:
In this specific case, the logic was implemented inside a Collector
and we tried to move it into a Query abstraction using a
TwoPhaseIterator with a high matchCost. The first-phase would match on
all docs (essentially:
Instead of a Collector, why isn't this a TwoPhaseIterator with a high
matchCost?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Thu, May 6, 2021 at 6:43 PM Michael Sokolov wrote:
> Thanks Adrien, that is something like what I had in mind. If you
