[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314219#comment-14314219
]
Terry Smith commented on LUCENE-6229:
-------------------------------------
Like Stefan, I'm also using this functionality to access child scorers on a per
document basis. Currently for some custom query enhancements and a custom drill
sideways implementation.
Like Adrien, I've also had to wrap queries in a custom NonBulkScoringQuery to
force doc-at-a-time scoring.
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.
I'd love to have a way to not only get the child scorers but be confident that
they were all correctly positioned.
> 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]
