has_child query can yield in wrong results if parent type has nested inner objects #4341
Assignees
Labels
Comments
ghost
assigned 
martijnvg
added a commit
that referenced
this issue
Dec 4, 2013
… parent type has nested object types. The inner objects (Separate Lucene docs) are also emitted as hits, which incorrectly decreased the count down short circuit mechanism in the `has_child` query. Closes #4341
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
… parent type has nested object types. The inner objects (Separate Lucene docs) are also emitted as hits, which incorrectly decreased the count down short circuit mechanism in the `has_child` query. Closes elastic#4341
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a parent type has nested inner objects then the
has_childquery (with score_mode) can return wrong results. This is caused by an internal short circuiting mechanism and the fact that hidden nested Lucene document have the same uid as the main document. The internal short circuiting mechanism sees the hidden nested Lucene document as a hit and starts the countdown for short circuiting from the wrong hits. This results in too less hits being returned.Relates to #4210 and is the reason why with ES version 1.0 beta2 too less results are being returned.
The text was updated successfully, but these errors were encountered: