zkendall commented on code in PR #2799: URL: https://github.com/apache/solr/pull/2799#discussion_r1820041702
########## solr/solr-ref-guide/modules/indexing-guide/pages/indexing-nested-documents.adoc: ########## @@ -304,6 +305,11 @@ Instead, use delete-by-query (most efficient) or xref:partial-document-updates.a If you use Solr's delete-by-query APIs, you *MUST* be careful to ensure that any deletion query is structured to ensure no descendent children remain of any documents that are being deleted. *_Doing otherwise will violate integrity assumptions that Solr expects._* +=== Shard Splits +When xref:deployment-guide:shard-management.adoc#splitshard[splitting shards], child documents get transmitted and routed on their own, since they are documents in their own right. If you route based on your unique field, then the child documents will be routed correctly based on their `_root_`. However, if your collection specifies a router field (even if it matches the unique field), then the child documents will be routed based on that field instead of their root field. If your collection specifies a router field, you should ensure every doc in a hierarchy has the same value for that field, otherwise it maybe broken during a shard split. Review Comment: Switched to humble little paragraph (with breadcrumb in title).  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
