[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14313722#comment-14313722
]
Stefan Pohl commented on LUCENE-6229:
-------------------------------------
Hi Adrian, Mike,
thanks for your recent efforts in cleaning up with many outstanding
refactorings.
I'm using this functionality in analytics/debugging contexts where it's not
necessary to have best possible performance (e.g. using BooleanScorer).
LUCENE-2590 doesn't seems to be a feature that you would assume Lucene to use
internally, and I doubt many actual users of this functionality track JIRA and
would speak up here.
Could this functionality be provided in a different way that doesn't have the
problems you want to address here? E.g. could users hint the search to require
this functionality (needClauses?), which in turn leads to not using optimized
implementations that cannot (easily) provide this information?
> 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]
