[
https://issues.apache.org/jira/browse/LUCENE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324686#comment-14324686
]
Terry Smith commented on LUCENE-6229:
-------------------------------------
[~rcmuir] Thanks for the backstory. I've been trying to wrap my head around
where Lucene is going and this kind of information really helps.
It sounds like both [~rcmuir] and [~thetaphi] agree that Scorer.getChildren()
is not an API that Lucene should support. Reading between the lines, this
implies to me that scoring is moving to a bulk-only approach, which will bring
great performance gains.
A best effort implementation of Scorer.getChildren() would be something that
I'd be uncomfortable adding features on top of, although it could be useful for
debugging. Unfortunately this is a showstopper for me as I rely on
Scorer.getChildren() for some critical features, and need to do some serious
thinking to figure out if I can formulate an alternative approach.
> 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
