-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Query parse failures not being returned as server errors #61
Comments
Fixed |
ywelsch
added a commit
to ywelsch/elasticsearch
that referenced
this issue
Jun 4, 2018
…elastic#61) Creates request / response objects with proper serialization logic for all network interactions with Legislator.
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we leverage new functionality in Rally to spin up a cluster before all challenges are executed. This allows us to run challenges which depend on others (e.g. query only challenges that rely on another challenge to actually put the data into the cluster). Closes elastic#49
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we enable verbose index writer logging via params instead of a special car. This reduces maintenance effort in rally-teams by eliminating a config base and a car. Relates elastic#61
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
If the search query doesn't parse correctly, the server should return a server error. Currently, it returns the errors in the response, but the status code is 200:
The text was updated successfully, but these errors were encountered: