[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318298#comment-14318298
]
Uwe Schindler commented on LUCENE-6229:
---------------------------------------
I agree,
actually only one of my customers really used this. And at the time they did
this, the API was already not perfect, and as Robert said - incomplete and not
guaranteed to work (Lucene 3 times) - e.g. it only worked if bulk scoring was
not enabled (the customer just passed correct booleans to weight, so it thought
that it was not top-level query). The API was really cool in Lucene 4+, but I
was never using it for real use cases.
The other (current) customer split ther query up already before the scorer was
invoved (they are interested in counts on sub querys) - so removal is not an
issue. The code used was actually written by [~simonw], I just inherited it :-)
> 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]
