-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Using a single 'Range' query inside a Query can cause a server side error #971
Comments
@kohner86 would you mind posting your code or an example which produces this error? |
Sure, Which generates the following error: |
This was a bug with FilteredQuery, and not Range. I just pushed the above fix. Thanks for reporting this! |
I'm also getting errors with the RangeQueryDescriptor when using OnField:
|
@BjBlazkowicz What is the error you're getting? |
Sorry gmarz, no exceptions and errors. My bad. But I think we should be able to set the timezone in the Range query? |
@BjBlazkowicz sorry this fell under my radar since the issue was closed. Yup, you are totally right, |
Not sure if this is by design but if I define a query with a single QueryDescriptor inside of type Range in which the 'OnField' value is null ES throws a QueryParsingException since the emitted JSON in the query is empty due to no queries being present.
It seems that the nest library will automatically inject a match_all into the query if none are specified but in the above case the match_all is not added.
In the mean time I've been able to stop the issue from popping up by putting the Range query in a boolean query paired with a match_all.
The text was updated successfully, but these errors were encountered: