[SPARK-46083][PYTHON] Make SparkNoSuchElementException as a canonical error API #43992
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 is a kind of a followup of #43927 which added
SparkNoSuchElementException
into errors. This PR makesSparkNoSuchElementException
as a canonical error API.Why are the changes needed?
For the end users to catch those exceptions properly via
pyspark.errors.SparkNoSuchElementException
with/without Spark Connect.Does this PR introduce any user-facing change?
Yes, it adds a new API
SparkNoSuchElementException
class.How was this patch tested?
Manually tested:
./bin/pyspark --remote local
Was this patch authored or co-authored using generative AI tooling?
No.