-
Notifications
You must be signed in to change notification settings - Fork 16
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
Fix #1383: map most recognized SERVER_ errors to 504 or 502, leave 500 for unrecognized #1384
Conversation
…0 for unrecognized
...java/io/stargate/sgv2/jsonapi/service/operation/collections/FindCollectionOperationTest.java
Show resolved
Hide resolved
.toApiException("(DriverException/ClosedConnectionException) %s", message) | ||
.getCommandResultError(Response.Status.GATEWAY_TIMEOUT); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why here is GATEWAY_TIMEOUT
not BAD_GATEWAY
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me double-check; you are right seems odd.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Hazel-Datastax yes, you are right: should be BAD_GATEWAY -- changing. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What this PR does:
Maps most former 500 http failures to 504 or 502, to indicate these are recognized failures with backend DB; 500 remains for unknown/unrecognized exceptions
Which issue(s) this PR fixes:
Fixes #1383
Checklist