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

Better handling of /_all/_search when no indices exist #3710

Closed
clintongormley opened this Issue Sep 16, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@clintongormley
Copy link
Member

clintongormley commented Sep 16, 2013

At the moment, a search against a cluster which has no indices will return a 503 Service Unavailable. This is a "big" error code which in other places means that a node or cluster is down.

Rather throw an IndexMissing exception with a 404. Similarly, the same should apply to count, mlt etc etc

@clintongormley

This comment has been minimized.

Copy link
Member Author

clintongormley commented Sep 16, 2013

Actually, my preference here (when searching on _all would be to return zero hits instead of throwing an error.

@kimchy

This comment has been minimized.

Copy link
Member

kimchy commented Sep 16, 2013

yea, that would also be consistent with our broadcast based APIs (like count, suggest, ...)

@ghost ghost assigned kimchy Sep 16, 2013

@kimchy kimchy closed this in 8f7e3c8 Sep 16, 2013

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.