[
https://issues.apache.org/jira/browse/LUCENE-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331820#comment-15331820
]
Mikhail Khludnev commented on LUCENE-7206:
------------------------------------------
Just a note, current approach might be too slow, it explains all children and
then pickups one of these explanation. For short blocks it's ok, but for longer
ones the two phase algorithm makes sense: find appropriate child (min/max or
so), and explain it only after that.
I prefer to keep it as a reminder, let's raise an issue if someone bother about
it too.
> nest child query explain into
> ToParentBlockJoinQuery.BlockJoinScorer.explain(int)
> ---------------------------------------------------------------------------------
>
> Key: LUCENE-7206
> URL: https://issues.apache.org/jira/browse/LUCENE-7206
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/query/scoring
> Affects Versions: 6.0
> Reporter: Mikhail Khludnev
> Labels: newbie, newdev
> Fix For: 6.1, master (7.0)
>
> Attachments: LUCENE-7206-one-child-with-tests.patch,
> LUCENE-7206-test.patch, LUCENE-7206.diff
>
>
> Now to parent query match is explained with {{Score based on child doc range
> from .. to .. }} that's quite useless.
> It's proposed to nest child query match explanation from the first matching
> child document into parent explain.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
