Refactor PythonException so it can take errorClass with sqlstate #53099
+58
−26
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
In general we want an
sqlstatewithPythonExceptionto be better categorized. This PR basically rewritePythonExceptiontoSparkPythonExceptionstyle. For now we report38000for all existing exceptions, but we leave the flexibility to future changes.Why are the changes needed?
Many reported PythonExceptions can't be categorized by
sqlstatewhich is not helpful to triage and build metrics.Does this PR introduce any user-facing change?
Yes.
I believe the exception report would be different.
sqlstatewill be there and the print format will be slightly changed.How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
No.