[
https://issues.apache.org/jira/browse/SOLR-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657301#comment-16657301
]
David Smiley commented on SOLR-12638:
-------------------------------------
[~caomanhdat] would you mind looking over the goals of this issue and sharing
any thoughts you may have on it's relationship to the UpdateLog or SolrCloud
(e.g. gotchas or advice / pointers)? Sorry that's a little vague... but I'm
trying to feel out unknown-unknowns that prevent me from asking a specific
question at this stage. I'm sure we can get our tests to pass by ourselves but
that's no guarantee against edge cases we don't even know about (either due to
circumstances of real-world behavior / timings / safety) or things we should
test for but didn't.
In summary we want atomic updates to support nested documents. This way you
could not only update existing parent/child documents but even add/remove
entire nested trees.
> 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 40m
> 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: [email protected]
For additional commands, e-mail: [email protected]
