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

Mapping SQLException of too many connection to TOO_MANY_REQUEST status #276

Merged
merged 1 commit into from
Jul 27, 2018

Conversation

zhljen
Copy link
Contributor

@zhljen zhljen commented Jul 24, 2018

No description provided.

@zhljen zhljen requested a review from ajoymajumdar July 24, 2018 21:37
@zhljen zhljen self-assigned this Jul 24, 2018
@zhljen zhljen added this to the 1.2.0 milestone Jul 24, 2018
@ajoymajumdar
Copy link
Contributor

Like other Metacat exceptions (MetacatException), we need to define an Exception specifically for 429. We should have this mapping of Pool exhaust error either in the connectors or in the controller RequestWrapper, instead of in the ExceptionMapper.

@zhljen zhljen force-pushed the master branch 3 times, most recently from d6ca11a to 842d643 Compare July 25, 2018 21:53
@zhljen
Copy link
Contributor Author

zhljen commented Jul 27, 2018

Updated to address comments.

@ajoymajumdar
Copy link
Contributor

Changes look good. You also want to modify com.netflix.metacat.client.module.MetacatErrorDecoder.

@zhljen
Copy link
Contributor Author

zhljen commented Jul 27, 2018

Updated based on suggestion.

@zhljen zhljen merged commit 91f0d40 into Netflix:master Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants