You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2016/03/04 09:43:40 UTC

[jira] [Commented] (LUCENE-7065) Fix explain for global ordinal query time join

    [ https://issues.apache.org/jira/browse/LUCENE-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179567#comment-15179567 ] 

Adrien Grand commented on LUCENE-7065:
--------------------------------------

Maybe the explanation descriptions should be more explicit: I think it could be interesting to know that a document has no join value vs. it has one but it does not match.

> Fix explain for global ordinal query time join
> ----------------------------------------------
>
>                 Key: LUCENE-7065
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7065
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Martijn van Groningen
>         Attachments: LUCENE_7065.patch
>
>
> The explain methods for the global ordinal join is broken, because even in the case that a document doesn't match with the query it tries to create an explain that tells it does. 
> In the case when score mode 'avg' is used this causes a NPE and in the other cases the return explanation indicates that a document matches while it doesn't.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org