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

ASF subversion and git services commented on SOLR-9288:
-------------------------------------------------------

Commit fee9526208375fec6a7651249b182fbca1a29703 in lucene-solr's branch 
refs/heads/branch_6x from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=fee9526 ]

SOLR-9180: More comprehensive tests of psuedo-fields for RTG and SolrCloud 
requests

This commit also includes new @AwaitsFix'ed tests for the following known 
issues...

 * SOLR-9285 ArrayIndexOutOfBoundsException when ValueSourceAugmenter used with 
RTG on uncommitted doc
 * SOLR-9286 SolrCloud RTG: psuedo-fields (like ValueSourceAugmenter, [shard], 
etc...) silently fails (even for committed doc)
 * SOLR-9287 single node RTG: NPE if score is requested
 * SOLR-9288 RTG: fl=[docid] silently missing for uncommitted docs
 * SOLR-9289 SolrCloud RTG: fl=[docid] silently ignored for all docs

(cherry picked from commit ae316f1e39e58d89758f997913a38059d74ccb47)


> RTG: fl=[docid] silently missing for uncommitted docs
> -----------------------------------------------------
>
>                 Key: SOLR-9288
>                 URL: https://issues.apache.org/jira/browse/SOLR-9288
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>
> Found in SOLR-9180 testing.
> when using RTG in a single node solr install, the {{\[docid\]}} transformer 
> works for committed docs, but is silently missing from uncommited docs.
> this inconsistency is confusing.  It seems like even if there is no valid 
> docid to return in this case, the key should still be present in the 
> resulting doc.
> I would suggest using either {{null}} or {{-1}} in this case?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to