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.

Sign up for GitHub

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

Jump to bottom

Errors resulting from Elasticsearch Timing out should yeild 504 Gateway Timeout errors, rather than plain old 500 errors. #91

Open
pgulley opened this issue Aug 20, 2024 · 0 comments
Open

Errors resulting from Elasticsearch Timing out should yeild 504 Gateway Timeout errors, rather than plain old 500 errors. #91

pgulley opened this issue Aug 20, 2024 · 0 comments
Assignees
@pgulley
Milestone
3 - August

Comments

@pgulley
Copy link
Member

pgulley commented Aug 20, 2024

In the spirit of improving performance, we should have errors thrown that reflect the error actually occuring- right now the api opines rather blithely about query formatting by default.
@pgulley pgulley added this to the 3 - August milestone Aug 20, 2024
@pgulley pgulley self-assigned this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pgulley pgulley

Labels
None yet
Projects
None yet
Milestone
3 - August
Development

No branches or pull requests
1 participant
@pgulley