[SPARK-52321] Add SessionClosed/SqlConfNotFound/ParseSyntaxError to SparkConnectError
#180
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
…or` to `SparkConnectError`
dongjoon-hyun
changed the title
SessionClosed, SqlConfNotFound, ParseSyntaxError to SparkConnectErrorSessionClosed/SqlConfNotFound/ParseSyntaxError to SparkConnectError
|
Let me merge this to move forward. |
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.
What changes were proposed in this pull request?
This PR aims to add
SessionClosed,SqlConfNotFound,ParseSyntaxErrortoSparkConnectError.Why are the changes needed?
To provide a user can catch these exceptions easily instead of matching
internalErrorwith string patterns.Does this PR introduce any user-facing change?
Yes, but these are more specific exceptions than before.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.