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

Query parse failures not being returned as server errors #61

Closed
clintongormley opened this issue Mar 12, 2010 · 1 comment
Closed

Query parse failures not being returned as server errors #61

clintongormley opened this issue Mar 12, 2010 · 1 comment

Comments

@clintongormley
Copy link
Contributor

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:

curl -XGET 'http://192.168.5.100:9200/_all/_search'  -d '
{
   "query" : {}
}
'
# {
#    "hits" : {
#       "hits" : [],
#       "total" : 0
#    },
#    "_shards" : {
#       "failures" : [
#          {
#             "index" : "ia_object",
#             "reason" : "SearchParseException[[ia_object][3]: quer
# >             y[null],from[-1],size[-1]: Parse Failure [Failed to
# >  parse [{\n   \"query\" : {}\n}\n]]]; nested: QueryParsingExcep
# > tion[[ia_object] No json query parser registered for [query]]; 
# > ",
#             "shardId" : 3
#          },
#          {
#             "index" : "ia_object",
#             "reason" : "SearchParseException[[ia_object][1]: quer
# >             y[null],from[-1],size[-1]: Parse Failure [Failed to
# >  parse [{\n   \"query\" : {}\n}\n]]]; nested: QueryParsingExcep
# > tion[[ia_object] No json query parser registered for [query]]; 
# > ",
#             "shardId" : 1
#          },
#          {
#             "index" : "ia_object",
#             "reason" : "SearchParseException[[ia_object][2]: quer
# >             y[null],from[-1],size[-1]: Parse Failure [Failed to
# >  parse [{\n   \"query\" : {}\n}\n]]]; nested: QueryParsingExcep
# > tion[[ia_object] No json query parser registered for [query]]; 
# > ",
#             "shardId" : 2
#          },
#          {
#             "reason" : "Unknown"
#          },
#          {
#             "reason" : "Unknown"
#          }
#       ],
#       "failed" : 5,
#       "successful" : 0,
#       "total" : 5
#    }
# }
@clintongormley
Copy link
Contributor Author

Fixed

dadoonet added a commit that referenced this issue Jun 5, 2015
#61 and #62 renamed settings by deprecating old ones and creating new ones.
In version 3.0.0, we can remove old settings.

That said, we should not remove it from master doc before 2.6.0 is released.

Closes #70.
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant