[jira] [Commented] (SOLR-13852) TestCloudNestedDocsSort can use the same uniqueKey for both a parent and child doc
[ https://issues.apache.org/jira/browse/SOLR-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953258#comment-16953258 ] ASF subversion and git services commented on SOLR-13852: Commit 3a67c82c9161454e3a7e6bf76cde7ed7e4018f28 in lucene-solr's branch refs/heads/branch_8x from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=3a67c82 ] SOLR-13852: Fix TestCloudNestedDocsSort to ensure child docs are never created in a way that violates uniqueKey rules (cherry picked from commit ebc720c5b09ae06b8ab093b296bf87e4f6ed978f) > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-13852) TestCloudNestedDocsSort can use the same uniqueKey for both a parent and child doc
[ https://issues.apache.org/jira/browse/SOLR-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953248#comment-16953248 ] ASF subversion and git services commented on SOLR-13852: Commit ebc720c5b09ae06b8ab093b296bf87e4f6ed978f in lucene-solr's branch refs/heads/master from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ebc720c ] SOLR-13852: Fix TestCloudNestedDocsSort to ensure child docs are never created in a way that violates uniqueKey rules > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
