Top_children not returning results

slushi · April 14, 2012, 6:36am

I am having an issue with the top_children query sporadically not
returning any results on 0.19.2. I have created a gist and linked it
below. I tried debugging the code - I can't say I really understand
what's going on but it looks like in QueryPhase.execute() the while
loop executes twice due to a lack of results. After the first
iteration, the parent doc is set in the context. Somehow during the
second iteration, the result doc is actually the parent (I checked the
doc id by using luke on the index) and the parentDocs map in the
context map is empty because TopChildrenQuery.processResults recreates
it on every call. Hopefully that makes sense and is helpful.

gist.github.com

https://gist.github.com/kireet/2382459

es_tcbug.sh

#!/bin/bash

echo "attempting index delete"
result=`curl -s -XDELETE 'http://localhost:9200/tcbug?pretty=true'`
echo "$result"

echo "attempting index creation"
result=`curl -s -XPOST 'http://localhost:9200/tcbug?pretty=true' -d '{
    "index": {
        "number_of_shards": 1,

This file has been truncated. show original

slushi · April 17, 2012, 7:12pm

I went ahead and opened a new issue:

github.com/elastic/elasticsearch

top_children not returning results when incremental child query required

opened 07:11PM - 17 Apr 12 UTC

closed 11:20AM - 12 Aug 13 UTC

kireet

I am facing an issue where a top_children query is not returning results when th…e code must issue an incremental child query to try to get more results. I think this is clearly a bug b/c when I set the size such that the first query suffices, results are returned for the same query. I have created a gist to reproduce the problem, basically it just creates an index with a single parent doc and multiple child docs. Then it does 2 top_children queries with identical queries but differing size, factor and incremental factor values. One returns results and the other doesn't. This is on 0.19.2 https://gist.github.com/2382459

On Saturday, April 14, 2012 2:36:59 AM UTC-4, slushi wrote:

I am having an issue with the top_children query sporadically not
returning any results on 0.19.2. I have created a gist and linked it
below. I tried debugging the code - I can't say I really understand
what's going on but it looks like in QueryPhase.execute() the while
loop executes twice due to a lack of results. After the first
iteration, the parent doc is set in the context. Somehow during the
second iteration, the result doc is actually the parent (I checked the
doc id by using luke on the index) and the parentDocs map in the
context map is empty because TopChildrenQuery.processResults recreates
it on every call. Hopefully that makes sense and is helpful.

elastic search bug when running top_children queries · GitHub