-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35397][SQL] Replace sys.err usage with explicit exception type #32535
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
| case _ => | ||
| sys.error("Unsupported natural join type " + joinType) | ||
| throw QueryExecutionErrors.unsupportedNaturalJoinTypeError(joinType) | ||
|
|
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.
nit. extra space.
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.
Removed. Thanks.
dongjoon-hyun
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.
Looks fine and consistent to me.
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #138503 has finished for PR 32535 at commit
|
srowen
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.
It will change the exception type, but, the exception generated now is uselessly broad anyway. I think it's fine.
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Merged to master for Apache Spark 3.2.0. |
|
Thank you @dongjoon-hyun @maropu @srowen |
|
Test build #138517 has finished for PR 32535 at commit
|
What changes were proposed in this pull request?
This patch replaces
sys.errusages with explicit exception types.Why are the changes needed?
Motivated by the previous comment #32519 (comment), it sounds better to replace
sys.errusages with explicit exception type.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.