# Various "nested" problems with elasticsearch 0.17.9 and 0.18.5

**URL:** <https://discuss.elastic.co/t/various-nested-problems-with-elasticsearch-0-17-9-and-0-18-5/6113>\
**Category:** Elasticsearch\
**Created:** [December 9, 2011, 8:47pm UTC](https://discuss.elastic.co/t/various-nested-problems-with-elasticsearch-0-17-9-and-0-18-5/6113 "2011-12-09T20:47:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_At\_Ikanow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_at_ikanow/32/676_2.png) [@Alex\_At\_Ikanow](https://discuss.elastic.co/u/Alex_At_Ikanow)\
**Post date:** [December 9, 2011, 8:47pm UTC](https://discuss.elastic.co/t/various-nested-problems-with-elasticsearch-0-17-9-and-0-18-5/6113/1 "2011-12-09T20:47:28Z")

</div>

Annoyingly I failed to reproduce the original problem I was debugging,  
but turned up 2 likely bugs along the way, one of which I think is  
significant, the other might be minor. I also believe the original bug  
was real even though I can't corroborate that.

1] An index type related problem (as in "http://:9200///"): might just be that the index type can't be  
named "nested" - if, looking at the code, that's not the case, then  
might be more serious. (observed on 0.18.5)

Steps to reproduce:

> <https://gist.github.com/Alex-Ikanow/1453137>

2] Delete by query doesn't appear to delete the nested objects  
(observed on 0.17.9 and 0.18.5):

> <https://gist.github.com/Alex-Ikanow/1453163>

Is there an easy workaround (eg for parent/child docs you could use  
something like "term": { "parent":"parent#" } to delete the  
children)?

3] The problem I observed on my dev cluster (0.17.9) that I failed to  
reproduce was something like:

- index 198 objects with 3204 nested "children" (ie 3302 docs total  
in the index)
- modify the objects originally inserted and reindex (just relying on  
overwrites - the "parent" \_ids are specified not auto generated)
- observe the number of docs is the same
- run any nested query and get exactly the same error/log exception  
described in [1]

I cannot reproduce this, either by retracing my steps on my dev  
cluster (0.17.9) or with simpler abstractions on my clean 0.18.5  
install.

I'd be happier it was the error hadn't been the same docset/null  
pointer exception from [1] ... somewhat suggesting there's some flaky  
somewhere logic that might fail but is not predictably guaranteed to!

Anyway, I'd be interested in your thoughts on [3], and let me know if  
you want me to create issues against [1] and [2]  
Important Disclaimer:  
This email or attachments may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:45am UTC](https://discuss.elastic.co/t/various-nested-problems-with-elasticsearch-0-17-9-and-0-18-5/6113/2 "2017-07-06T03:45:55Z")

</div>

Closed on July 6, 2017, 3:45am UTC