Provide a brief overview of what the new feature is all about
If a _view has an impossible start_key/end_key combination we send a helpful error;
{"error":"query_parse_error","reason":"No rows can match your key range, reverse your start_key and end_key or set descending=false","ref":457284027}
We should do the same for _all_docs
Tell us how the new feature should work. Be specific
A similar check_range function when parsing query params of _all_docs calls, returning a 400 status code and the same error reason as for _view.
Not required. Suggest how to implement the addition or change
No response
Additional Context
No response