Wrapping all curator exceptions in RuntimeExceptions. #671
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can we change this to only wrap the exception in a RuntimeException if it's not already a RuntimeException? |
|
Done. |
nathanmarz
added a commit
that referenced
this pull request
Sep 19, 2013
Wrapping all curator exceptions in RuntimeExceptions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently we ran into a situation where an InterruptedException was being thrown from IOutputCollector.reportError, even though InterruptedException is not a RuntimeException. Many of the Curator APIs actually declare that any Exception can be thrown. To avoid non-runtime exceptions being thrown by a java API that does not declare it, this patch wraps any Exception thrown by the curator API in a RuntimeException.