[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318272#comment-14318272
]
Terry Smith commented on LUCENE-6229:
-------------------------------------
[~jpountz] - I'm going to split the freq() vs score() thing into a separate
ticket so it doesn't hijack this one. I intend to take the unit test I
previously pasted and extend it to create some randomized BooleanQuerys to try
and locate possibly broken edge cases and give a safety blanket for future
refactoring.
I'll make these assumptions, shout out if they are incorrect.
For a BooleanQuery I should be able to perform doc-at-a-time scoring, meaning
that in a Collector or Scorer I can
1. Find all Scorers from the child clauses of the BooleanQuery
2. Have those Scorers be positioned for me by calling score() or freq()
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
