-
Notifications
You must be signed in to change notification settings - Fork 9k
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
HDFS-17746. [ARR] The behavior of throwing exception in getListing should be consistent with sync mode. #7464
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
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.
+1. LGTM.
@KeeProMise Sir, also cc please. Thanks a lot. |
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!
@Hexiaoqiao @KeeProMise Sir, thanks a lot for reviewing. |
…ould be consistent with sync mode.
bc6fb0a
to
7305cdc
Compare
Rebase this pr onto trunk, waiting for pipeline building. |
🎊 +1 overall
This message was automatically generated. |
Description of PR
The behavior of throwing exception in getListing should be consistent with sync mode.
In this scene, NoLocationException or RouterResolveException could only be thrown by getLocationsForPath which does not issue any rpc. So we need not use asyncTry.
How was this patch tested?
Add an unit test.