[ 
https://issues.apache.org/jira/browse/SOLR-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758647#comment-16758647
 ] 

ASF subversion and git services commented on SOLR-5211:
-------------------------------------------------------

Commit 46151b29be621af49a90f271f60d3c3549aecedb in lucene-solr's branch 
refs/heads/branch_8_0 from David Wayne Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=46151b2 ]

SOLR-5211: Document that delete-by-id (and updates) don't affect child/nested 
docs

(cherry picked from commit 372d68f7f68a5a9238fdfbddeae6488432795603)


> 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, SOLR-5211_docs.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

Reply via email to