[
https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498834#comment-16498834
]
David Smiley commented on SOLR-5211:
------------------------------------
bq. It should be relatively trivial to know if the _root_ field exists in the
index (i.e. when any parent/child groups exist) and do the right thing based on
that.
How then do you handle the first document? What if circumstantially the first
doc is a doc with children... then you add \_root_? Okay but if
circumstantially the first doc has no children then....? Or maybe your
comment is how do we handle an existing index before this rule existed? I'm
not sure it's worth troubling ourselves over that... maybe instead log a
warning on startup if _root_ is defined and some (but not all) docs have it.
I assume that the goal is for an index in which _every_ document has _root_
(and is thus parent/child enabled), or none do and there are no child docs.
Partial is asking for trouble.
> 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: Mikhail Khludnev
> Priority: Major
> Attachments: SOLR-5211.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
