Sujay,

Not really. Parent-child documents are stored in a single block
contiguously. Read more about parent-child relationship at:
https://medium.com/@sarkaramrit2/multiple-documents-with-same-doc-id-in-index-in-solr-cloud-32c072db2164

While we perform partial / atomic update, say {"id":"X",
"fieldA":{"set":"Z"}, that particular doc with X will be fetched (all the
"stored" fields), update will be performed and indexed, all happens in
*DistributedUpdateProcessor* internally. So there is no way it will fetch
the child documents along with it.

I am not sure whether this can be done with current code or it will be
fixed / improved in the future.

Amrit Sarkar
Search Engineer
Lucidworks, Inc.
415-589-9269
www.lucidworks.com
Twitter http://twitter.com/lucidworks
LinkedIn: https://www.linkedin.com/in/sarkaramrit2

On Mon, Jul 17, 2017 at 12:44 PM, Sujay Bawaskar <[EMAIL PROTECTED]>
wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB