I'm not sure if this query is valid or not, but regardless, I'm getting a
400 from the search api and a 200 from the count API. It seems like they
should be consistent.
The output from this gist is:
Count using a good query
Search using a good query
Count using a bad query
Search using a bad query
If you take out the "-o /dev/null", you can see that both the search and
count produce errors in the "bad query" case, but the count API still
returns a 200.
On a related note, is it expected that putting "*field_name:field_value" in
a query string should produce a parse exception?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.