The reason why you receive a SearchPhaseExecutionException and many SearchParseExceptions is that your query is parsed at each shard and causes an error at that deeper level. ES wraps up the shards responses into a SearchPhaseExecutionException which is passed back to the client.
In most cases, all shards respond with same errors, but that is not always the case. This certainly can be improved regarding the JSON formatting by a patch to ES so the REST action tries to parse error response from shards. Another possibility would be processing the shards exceptions and just returning a short SearchPhaseExecutionException message saying something like "no query registered for ..." if all shard errors match. In general, I would simply rely on the REST response codes (here: 400) which signals "bad request" and ignore the ES error messages since they are fluctuating. Jörg -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEgmRHYXe6-9XaDrHjDPeb2Xq7%3D8bumetxAFcXbFHiB3Q%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
