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

Adi Kaminski commented on SOLR-12638:
-------------------------------------

So, in order to support integrity between parent-child document when parent or 
child documents atomically updated, the schema should have the following 3 
prerequisites ?

1. <field name="_root_" type="string" indexed="true" stored="*true*" 
docValues="false" />

2. <fieldType name="_nest_path_" class="solr.NestPathField" />

3. <field name="_nest_path_" type="_nest_path_" />

     Should _nest__path field have any additional attributed like stored=true, 
docValues, others ?

 

Any other special prerequisites for the indexing syntax ? Should 
_childDocuments used when indexing new parent-child documents or any other 
syntax ?

[https://builds.apache.org/job/Solr-reference-guide-master/javadoc/indexing-nested-documents.html#json-examples]

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to