[ https://issues.apache.org/jira/browse/SOLR-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658983#comment-16658983 ]
mosh commented on SOLR-12638: ----------------------------- {quote}Or, perhaps we insist the user send a _route_ parameter to /update which is otherwise only used in searches?{quote} I like this option a lot better, since it makes the updated doc look cleaner. Adding another field to the update command can seem a little confusing IMO, since that field is not used to update the document in any way. I just pushed a commit implementing this. > 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 > Priority: Major > Attachments: SOLR-12638-delete-old-block-no-commit.patch, > SOLR-12638-nocommit.patch > > Time Spent: 4h 50m > 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