[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314234#comment-14314234
]
Adrien Grand commented on LUCENE-6229:
--------------------------------------
bq.
bq. It'd be great to simplify this workflow as I've been calling Scorer.freq()
to position all the child scorers (from a BooleanQuery) and as of the 5.1
nightly builds am needing to call Scorer.score() instead for positioning due to
changes in MinShouldMatchSumScorer.
This is weird, both freq() and score() should position all sub scorers the same
way with MinShouldMatchSumScorer. What do your query and collector look like?
> Remove Scorer.getChildren?
> --------------------------
>
> Key: LUCENE-6229
> URL: https://issues.apache.org/jira/browse/LUCENE-6229
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
>
> This API is used in a single place in our code base:
> ToParentBlockJoinCollector. In addition, the usage is a bit buggy given that
> using this API from a collector only works if setScorer is called with an
> actual Scorer (and not eg. FakeScorer or BooleanScorer like you would get in
> disjunctions) so it needs a custom IndexSearcher that does not use the
> BulkScorer API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
