Christine Poerschke commented on SOLR-11164:

[~yuyano], [~Jonathan GV], [~ryac]
Thank you for reporting and looking into this here (SOLR-11164) and on 
SOLR-11180 and SOLR-11220 tickets.

bq. ... it is not the score from the original query. ...

Perhaps we could extend the test to compare the {{original}} feature value 
returned in the {{fl}} with the {{score}} returned in {{fl}} when LTR was not 
(With that in mind in SOLR-11223 i went and extended the TestLTROnSolrCloud 
coverage in two parts: part 1 includes the addition of local 
_original_resultX_score_ variables capturing the original {{score}} but part 2 
is unexpectedly failing i.e. if {{rq}} is not specified then no features are 

> OriginalScoreFeature causes NullPointerException during feature logging with 
> SolrCloud mode.
> --------------------------------------------------------------------------------------------
>                 Key: SOLR-11164
>                 URL: https://issues.apache.org/jira/browse/SOLR-11164
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: contrib - LTR
>    Affects Versions: 6.6
>            Reporter: Yuki Yano
>         Attachments: 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to