[SPARK-51178][CONNECT][PYTHON] Raise proper PySpark error instead of SparkConnectGrpcException
#49953
Conversation
This file contains 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
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 propose to raise proper PySpark error instead of
SparkConnectGrpcException.This PR also introduces new PySpark error
PickleExceptionto cover the errors that represents an exception which is failed while pickling from server sideWhy are the changes needed?
To raise proper exception instead of
SparkConnectGrpcExceptionDoes this PR introduce any user-facing change?
No API changes, but the user-facing error improvement.
How was this patch tested?
Updated the existing UT
Was this patch authored or co-authored using generative AI tooling?
No