[
https://issues.apache.org/jira/browse/LUCENE-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved LUCENE-9938.
----------------------------------
Resolution: Invalid
Nevermind. The TPI design requires that the "approximation" DISI coupled with
it is positioned, because TPI.matches() is no-arg and thus relies on the
approximation's position. Maybe the issue is still valid for other scenarios
not coupled with a TPI but I can't think of any. I wish the TPI design were
different; alas.
> ConjunctionDISI should recognize DocIdSetIterator.all
> -----------------------------------------------------
>
> Key: LUCENE-9938
> URL: https://issues.apache.org/jira/browse/LUCENE-9938
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: David Smiley
> Priority: Major
>
> ConjunctionDISI creates an aggregation of some leaf DocIdSetIterators &
> TwoPhaseIterators. It's not uncommon for DocIdSetIterator.all(...) to wind
> up inside it, producing an aggregation that is a little more bulky than it
> needs be. This can happen frequently with the ValueSource APIs which have
> queries like FunctionMatchQuery that use this for the "approximation"
> alongside a TwoPhaseIterator.
--
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
