You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/07/23 02:03:00 UTC
[jira] [Commented] (LUCENE-10000) MultiCollectorManager should have
parity with MultiCollector behavior
[ https://issues.apache.org/jira/browse/LUCENE-10000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385845#comment-17385845 ]
ASF subversion and git services commented on LUCENE-10000:
----------------------------------------------------------
Commit ad7746d6e31b698dd0f7d124288de576b4f95686 in lucene's branch refs/heads/main from Greg Miller
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=ad7746d ]
LUCENE-10000: Make MultiCollectorManager consistent with MultiCollector (#196)
MultiCollectorManager is now consistent with MultiCollector with respect to
early termination, min score setting and score caching.
> MultiCollectorManager should have parity with MultiCollector behavior
> ---------------------------------------------------------------------
>
> Key: LUCENE-10000
> URL: https://issues.apache.org/jira/browse/LUCENE-10000
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: main (9.0)
> Reporter: Greg Miller
> Assignee: Greg Miller
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The behavior of {{MultiCollectorManager}} and {{MultiCollector}} differ with respect to how they handle {{CollectionTerminationException}} and minCompetitiveScore calls.
> In {{MultiCollector}}, remaining collectors will continue collecting when one or more have thrown a {{CollectionTerminationException}}, but {{MultiCollectorManager}} will allow the exception to propagate and stop collecting against all collectors as soon as one throws (see: LUCENE-6772).
> Also, {{MultiCollector}} properly handles setting of min competitive scores by ensuring the lowest set across all wrapped collectors is used, or by making it a no-op in cases where at least one collector is using {{ScoreMode.COMPLETE}} (see: LUCENE-9402). {{MultiCollectorManager}} will share the same {{Scorable}} across all collectors, which seems like the wrong thing to do.
> Finally, {{MultiCollector}} will cache scores when a {{Scorable}} is shared by more than one collector (see: LUCENE-6263).
> We should update {{MultiCollectorManager}} to use common behavior with {{MultiCollector}} in all these areas. It should be easy to do by delegating to {{MultiCollector}} within {{MultiCollectorManager}}.
--
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