[SOLR-5211] updating parent as childless makes old children orphans

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.5, 6.0
• Fix Version/s: 8.0
• Component/s: update
• Assignee: David Smiley
• Reporter: Mikhail Khludnev
• Created: 03/Sep/13 18:19
• Updated: 29/Jul/21 16:54
• Resolved: 01/Feb/19 20:31

Description

if I have parent with children in the index, I can send update omitting children. as a result old children become orphaned.
I suppose separate _root_ fields makes much trouble. I propose to extend notion of uniqueKey, and let it spans across blocks that makes updates unambiguous.
WDYT? Do you like to see a test proves this issue?

Issue Links

• causes: SOLR-15540 changes in internal usage of _root_ field cause failures to deleteById or duplicate docs when updating after upgrading from Solr7 to Solr8
• is duplicated by: SOLR-6700 ChildDocTransformer doesn't return correct children after updating and optimising solr index
• is related to: SOLR-5772 duplicate documents between solr "block join" documents and "normal" document
• is related to: SOLR-7606 ToParentBlockJoinQuery fails with AIOOBE under certain circumstances
• is related to: SOLR-6596 Atomic update and adding child doc not working together
• is related to: SOLR-6096 Support Update and Delete on nested documents
• is related to: SOLR-10144 redesign block-join support
• is required by: SOLR-12638 Support atomic updates of nested/child documents for nested-enabled schema
• is superceded by: SOLR-7672 introduce implicit _parent_:true
• relates to: SOLR-3076 Solr(Cloud) should support block joins
• relates to: SOLR-13062 SimpleBlockJoinUpdateRequestProcessorFactory for Atomic update and adding child doc
• links to: GitHub Pull Request #501
• links to: GitHub Pull Request #501