Skip to content
This repository

Add better error handling for has_child, has_parent and top_children. #2261

Closed
martijnvg opened this Issue September 18, 2012 · 0 comments

1 participant

Martijn van Groningen
Martijn van Groningen
Owner

If has_parent, has_child or top_children are executed incorrectly then throw a better exception instead of the NPE that is currently being thrown. This happens now when one of these queries / filters are used in the count api.

Martijn van Groningen martijnvg referenced this issue from a commit in martijnvg/elasticsearch September 18, 2012
Martijn van Groningen Added better error handling for has_child, has_parent and top_children.
If has_parent, has_child or top_children are executed incorrectly then a better exception is thrown. This gives a better error description when one of these queries or filters is being used in count api.

Closes #2261
6cd64fd
Martijn van Groningen martijnvg closed this issue from a commit September 18, 2012
Martijn van Groningen Added better error handling for has_child, has_parent and top_children.
If has_parent, has_child or top_children are executed incorrectly then a better exception is thrown. This gives a better error description when one of these queries or filters is being used in count api.

Closes #2261
d5aa35e
Martijn van Groningen martijnvg closed this in d5aa35e September 18, 2012
Martijn van Groningen martijnvg referenced this issue from a commit September 18, 2012
Martijn van Groningen Added better error handling for has_child, has_parent and top_children.
If has_parent, has_child or top_children are executed incorrectly then a better exception is thrown. This gives a better error description when one of these queries or filters is being used in count api.

Closes #2261
9b3209b
Alberto Paro aparo referenced this issue from a commit May 31, 2013
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.