[SPARK-55727][PYTHON] Remove nested exception throwing in streaming data source error handling#54527
Open
allisonwang-db wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-55727][PYTHON] Remove nested exception throwing in streaming data source error handling#54527allisonwang-db wants to merge 1 commit intoapache:masterfrom
allisonwang-db wants to merge 1 commit intoapache:masterfrom
Conversation
allisonwang-db
force-pushed
the
streaming-error-refactor
branch
from
fcf2853 to
78c7ad6
Compare
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?
Refactor Python streaming data source error handling to throw PythonException instead of a wrapping it using the PYTHON_STREAMING_DATA_SOURCE_RUNTIME_ERROR error class.
Why are the changes needed?
Make error message simpler.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests
Was this patch authored or co-authored using generative AI tooling?
Yes