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

Ronen Nussbaum commented on SOLR-12638:
---------------------------------------

While child documents are updated as expected, updating a parent seems to break 
the connection to the child documents.
 # I've followed the [tutorial|http://example.com/] to get a running cloud 
cluster.
 # I indexed two documents with nested child documents, by copying the examples 
from [here|[http://yonik.com/solr-nested-objects/] [].|http://example.com]./]
 # In Solr Admin "Documents" page, I've sent an update request:

{code:java}
{"id":"book2" ,"cat_ss":{"set": "fantasy" }}
{code}

 # Query for parent with children:

{code:java}
http://localhost:8983/solr/gettingstarted/select?fl=*,[child 
parentFilter=type_s:book limit=1000]&q=id:book2
{code}

The response does not contain "_childDocuments_" element.

Did I miss something?

Thanks in advance.

 

> 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