[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020732#comment-15020732
]
Mikhail Khludnev commented on LUCENE-6229:
------------------------------------------
[~jpountz] our custom logic also extensively uses {{getChildren()}} we analyze
hits across all hits, not only top ones.
It somehow similar to LUCENE-1999
http://lucene.472066.n3.nabble.com/Highlighting-catering-for-all-query-types-td572693.html
Surely. We have to deal with suppressing term-at-time scorer, and sub-scorers
positioning. It lacks of design beauty but it works while we have
{{getChildren()}}.
> 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]
