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

David Smiley commented on SOLR-12638:
-------------------------------------

This is water under the bridge now, so to speak, but I thought I'd mention that 
this issue could have gone in smoother incrementally if the work was split up 
as follows:
 * add `[child]` support to RTG – SOLR-9006
 * atomic updates for nested docs, but only when the doc given in the update is 
a root doc.  Quite useful on its own.
 * atomic updates when the doc given is a child doc, and thus we need to pass a 
{{\_route_}} param so that it can go to the right shard.  This is more advanced.

> Support atomic updates of nested/child documents for nested-enabled schema
> --------------------------------------------------------------------------
>
>                 Key: SOLR-12638
>                 URL: https://issues.apache.org/jira/browse/SOLR-12638
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: 8.1
>
>         Attachments: SOLR-12638-delete-old-block-no-commit.patch, 
> SOLR-12638-nocommit.patch, SOLR-12638.patch, SOLR-12638.patch
>
>          Time Spent: 15.5h
>  Remaining Estimate: 0h
>
> I have been toying with the thought of using this transformer in conjunction 
> with NestedUpdateProcessor and AtomicUpdate to allow SOLR to completely 
> re-index the entire nested structure. This is just a thought, I am still 
> thinking about implementation details. Hopefully I will be able to post a 
> more concrete proposal soon.



--
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