zkendall opened a new pull request, #2799:
URL: https://github.com/apache/solr/pull/2799

   https://issues.apache.org/jira/browse/SOLR-11191
   
   # Description
   Prior to this, nested documents could get mis-routed during a the SPLITSHARD 
command. This results in violated integrity with children ending up on 
different shards than their parents and being loaded by the [child] transformer 
onto unintended parents.
   
   # Solution
   If the schema `isUsableForChildDocs` then we tell the shard splitter to use 
_root_ instead, which is populated with the unique field value of the top 
parent in the nested hierarchy. This ensures that the entire hierarchy gets 
colocated during the split.
   
   # Tests
   I have added two tests that add nested documents to a shard. I split the 
shard, and verify the nested relationship integrity is maintained.
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my 
code conforms to the standards described there to the best of my ability.
   - [ ] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [ ] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended, not available for 
branches on forks living under an organisation)
   - [ ] I have developed this patch against the `main` branch.
   - [x] I have run `./gradlew check`.
   - [x] I have added tests for my changes.
   - [x] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to