-
Notifications
You must be signed in to change notification settings - Fork 168
Cleanup RuntimeException and fetchRemoteStorage logic in ClientUtils #295
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #295 +/- ##
============================================
+ Coverage 60.10% 61.31% +1.20%
+ Complexity 1413 1291 -122
============================================
Files 175 162 -13
Lines 9082 7830 -1252
Branches 872 754 -118
============================================
- Hits 5459 4801 -658
+ Misses 3331 2767 -564
+ Partials 292 262 -30 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
| public static Long getBlockId(long partitionId, long taskAttemptId, long atomicInt) { | ||
| if (atomicInt < 0 || atomicInt > Constants.MAX_SEQUENCE_NO) { | ||
| throw new RuntimeException("Can't support sequence[" + atomicInt | ||
| throw new IllegalArgumentException("Can't support sequence[" + atomicInt |
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.
RssException may be better. Because we will collect the RssException to judge the failure apps caused by RSS.
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.
The root cause of this problem is illegal argument, perhaps new RssException(msg, new IllegalArgumentException())?
RssException may be better. Because we will collect the RssException to judge the failure apps caused by RSS.
For this use case, I think warpping exception outside may be better, for example:
try {
run_rss();
} catch (e) {
throw new RssException(msg, e);
}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.
The root cause of this problem is illegal argument, perhaps
new RssException(msg, new IllegalArgumentException())?RssException may be better. Because we will collect the RssException to judge the failure apps caused by RSS.
For this use case, I think warpping exception outside may be better, for example:
try { run_rss(); } catch (e) { throw new RssException(msg, e); }
Make Sense.
|
|
jerqi
left a comment
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, thanks @kaijchen
|
Thanks @jerqi for the review. |
What changes were proposed in this pull request?
RuntimeExceptionwith proper specific subclass ofRuntimeException.ClientUtils#fetchRemoteStorage().Why are the changes needed?
RuntimeExceptionis not a good practice because it's difficult to catch (without catching other RE).Does this PR introduce any user-facing change?
No.
How was this patch tested?
ClientUtilsTest is modified to assert more specific exceptions.