[jira] [Updated] (SOLR-13852) TestCloudNestedDocsSort can use the same uniqueKey for both a parent and child doc

["Chris M. Hostetter (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris M. Hostetter updated SOLR-13852:
--------------------------------------
    Attachment: thetaphi_Lucene-Solr-master-Linux_24903.log.txt
        Status: Open  (was: Open)

attaching a jenkins log w/seed showing how this can cause failures due to the assertion logic introduced in SOLR-13851

> TestCloudNestedDocsSort can use the same uniqueKey for both a parent and child doc
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-13852
>                 URL: https://issues.apache.org/jira/browse/SOLR-13852
>             Project: Solr
>          Issue Type: Test
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Priority: Major
>         Attachments: thetaphi_Lucene-Solr-master-Linux_24903.log.txt
>
>
> TestCloudNestedDocsSort uses randomly generated "id" values for all docs, which not only means that two "parent" docs can be indexed with the same "id" value, but also that a child doc might be indexed with the same "id" value as a parent doc.
> While nothing in Solr actively prevents this, it's documented as something people shouldn't do, and can cause problems.
> In particular, this has caused some assertion failures for some test seeds due to how it interacts with SOLR-13851



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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