You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2019/10/16 23:06:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Chris M. Hostetter resolved SOLR-13852.
---------------------------------------
Fix Version/s: master (9.0)
8.4
Assignee: Chris M. Hostetter
Resolution: Fixed
> 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
> Assignee: Chris M. Hostetter
> Priority: Major
> Fix For: 8.4, master (9.0)
>
> 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