lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-11164) OriginalScoreFeature causes NullPointerException during feature logging with SolrCloud mode.
Date Fri, 25 Aug 2017 14:36:00 GMT


ASF subversion and git services commented on SOLR-11164:

Commit 492265014b549d5517e5ec25ffdd0e5557a4ed39 in lucene-solr's branch refs/heads/master
from [~cpoerschke]
[;h=4922650 ]

SOLR-11164, SOLR-11180, SOLR-11220: Fix NullPointerException and always-returns-zero contrib/ltr
OriginalScoreFeature issues in SolrCloud mode.
(Yuki Yano, Jonathan Gonzalez, Ryan Yacyshyn, Christine Poerschke)

> OriginalScoreFeature causes NullPointerException during feature logging with SolrCloud
> --------------------------------------------------------------------------------------------
>                 Key: SOLR-11164
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: contrib - LTR
>    Affects Versions: 6.6
>            Reporter: Yuki Yano
>            Assignee: Christine Poerschke
>         Attachments: SOLR-11164_master.patch, SOLR-11164_master_v2.patch, SOLR-11164.patch,
SOLR-11164.patch, SOLR-11164.patch
> In FeatureTransfer, OriginalScoreFeature uses original Query instance preserved in LTRScoringQuery
for the evaluation.
> This query is set in RankQuery#wrap during QueryComponent#process.
> With SolrCloud mode, document searches take two steps: finding top-N document ids, and
filling documents of found ids.
> In this case, FeatureTransformer works in the second step and tries to extract features
with LTRScoringQuery built in QueryComponent#prepare.
> However, because the second step doesn't call QueryComponent#process, the original query
of LTRScoringQuery remains null and this causes NullPointerException while evaluating OriginalScoreFeature.
> We can get the original query from ResultContext which is an argument of DocTransformer#setContext,
thus this problem can solve by using it if LTRScoringQuery doesn't have correct original query.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message