[
https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744445#comment-16744445
]
David Smiley commented on SOLR-5211:
------------------------------------
{quote}I'm unclear on your meaning. I would think the default behavior when
deleting a parent (regardless of by id or by query) should also delete its
children, to avoid ending up with orphans.
{quote}
That would certainly be nice but it's a technical challenge that we don't have
a solution for. In this issue we've tackled delete-by-id only (and for
better/worse it only works on a top/root doc). If you have ideas on
delete-by-query then I suggest filing a new issue.
> updating parent as childless makes old children orphans
> -------------------------------------------------------
>
> Key: SOLR-5211
> URL: https://issues.apache.org/jira/browse/SOLR-5211
> Project: Solr
> Issue Type: Sub-task
> Components: update
> Affects Versions: 4.5, 6.0
> Reporter: Mikhail Khludnev
> Assignee: David Smiley
> Priority: Blocker
> Fix For: 8.0
>
> Attachments: SOLR-5211.patch, SOLR-5211.patch, SOLR-5211.patch,
> SOLR-5211.patch, SOLR-5211.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
