[
https://issues.apache.org/jira/browse/LUCENE-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362719#comment-17362719
]
Adrien Grand commented on LUCENE-10001:
---------------------------------------
When would it be desirable that terminating collection on a collector also
terminates collection on other collectors that are wrapped under the same
MultiCollector? This sounds counter-intuitive to me as only the collector
itself can know when it has visited all the hits it needs? I also don't like
that collectors would return different results depending on what other
collectors are wrapped under the same MultiCollector?
> Make CollectionTerminatedException handling in MultiCollector configurable
> --------------------------------------------------------------------------
>
> Key: LUCENE-10001
> URL: https://issues.apache.org/jira/browse/LUCENE-10001
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: main (9.0)
> Reporter: Greg Miller
> Assignee: Greg Miller
> Priority: Minor
>
> In LUCENE-6772, {{MultiCollector}} was modified to continue collecting
> against other leaf collectors that had not thrown a
> {{CollectionTerminatedException}} in cases where another one does. It would
> be nice if this behavior could be configurable. Some use-cases might actually
> want to early terminate all leaf collectors as soon as one signals early
> termination.
> We could add a configurable option to the {{MultiCollector#wrap}} factory
> methods that allows users to specify the behavior they want.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
