[
https://issues.apache.org/jira/browse/SOLR-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894821#comment-16894821
]
David Smiley commented on SOLR-12638:
-------------------------------------
RE schema: Yes that's right Adi. No special additional attributes need to be
specified on nest_path; internally NestPathField uses appropriate settings so
that you needn't worry about it.
When providing documents to Solr when you have a nest_path, don't use
\_childDocuments_ any longer. I'm not sure if using that syntax has issues
with partial updates; maybe. Instead, use a fake field name that represents
the relationship meaningfully. Some examples are in the ref guide on that very
page you linked (search "content").
> 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
> 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: 17h 10m
> 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.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
