Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The top_children, has_child and has_parent query can cause error when cached. #3290

Closed
martijnvg opened this Issue Jul 3, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@martijnvg
Copy link
Member

martijnvg commented Jul 3, 2013

In the case that the top_children, has_child or has_parent queries are cached via the fquery filter then an class cast exception error occurs.

@ghost ghost assigned martijnvg Jul 3, 2013

martijnvg added a commit that referenced this issue Jul 3, 2013

Fixes class cast exception when`top_children`, `has_child` and `has_p…
…arent` queries are cached via `fquery` filter.

The error only occurs for `has_child` and `has_parent` if `score_mode` is used.
Closes #3290

@martijnvg martijnvg closed this in 4c8f3de Jul 3, 2013

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Fixes class cast exception when`top_children`, `has_child` and `has_p…
…arent` queries are cached via `fquery` filter.

The error only occurs for `has_child` and `has_parent` if `score_mode` is used.
Closes elastic#3290
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.