[jira] [Created] (LUCENE-7707) Only assign ScoreDoc#shardIndex if it was already assigned to non default (-1) value

["Simon Willnauer (JIRA)" <ji...@apache.org>]

Simon Willnauer created LUCENE-7707:
---------------------------------------

             Summary: Only assign ScoreDoc#shardIndex if it was already assigned to non default (-1) value
                 Key: LUCENE-7707
                 URL: https://issues.apache.org/jira/browse/LUCENE-7707
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Simon Willnauer
             Fix For: master (7.0), 6.5.0


When you use TopDocs.merge today it always overrides the ScoreDoc#shardIndex value. The assumption that is made here is that all shard results are merges at once which is not necessarily the case. If for instance incremental merge phases are applied the shard index doesn't correspond to the index in the outer TopDocs array. To make this a backwards compatible but yet non-controversial change we could change the internals of TopDocs#merge to only assign this value unless it's not been assigned before to a non-default (-1) value to allow multiple or sparse top docs merging.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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