[SPARK-46226][PYTHON] Migrate all remaining RuntimeError into PySpark error framework.#44143
Closed
itholic wants to merge 7 commits intoapache:masterfrom
Closed
[SPARK-46226][PYTHON] Migrate all remaining RuntimeError into PySpark error framework.#44143itholic wants to merge 7 commits intoapache:masterfrom
RuntimeError into PySpark error framework.#44143itholic wants to merge 7 commits intoapache:masterfrom
Conversation
…k error framework
itholic
changed the title
RuntimeErrors into PySpark error framework.RuntimeError into PySpark error framework.
Contributor
Author
|
This is the last one migrating error class that has not been reviewed yet. cc @HyukjinKwon @dongjoon-hyun Would you mind taking a look when you find some time 😺 |
HyukjinKwon
approved these changes
Dec 6, 2023
Member
|
Merged to master. |
dbatomic
pushed a commit
to dbatomic/spark
that referenced
this pull request
Dec 11, 2023
…rk error framework ### What changes were proposed in this pull request? This PR proposes to migrate all remaining `RuntimeError` from `pyspark/sql/*` into PySpark error framework, `PySparkRuntimeError` with assigning dedicated error classes. Total 30 `RuntimeError`s are managed. ### Why are the changes needed? To improve the error handling in PySpark. ### Does this PR introduce _any_ user-facing change? No API changes, but the user-facing error messages will be improved. ### How was this patch tested? The existing CI should pass. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#44143 from itholic/session_custom_error. Authored-by: Haejoon Lee <haejoon.lee@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
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
2 participants
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 proposes to migrate all remaining
RuntimeErrorfrompyspark/sql/*into PySpark error framework,PySparkRuntimeErrorwith assigning dedicated error classes. Total 30RuntimeErrors are managed.Why are the changes needed?
To improve the error handling in PySpark.
Does this PR introduce any user-facing change?
No API changes, but the user-facing error messages will be improved.
How was this patch tested?
The existing CI should pass.
Was this patch authored or co-authored using generative AI tooling?
No.