[SPARK-49392][SQL][FOLLOWUP] Catch errors when failing to write to external data source #48165
+3
−3
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
Contributor
|
Can you link the PR with test changes here please? |
uros-db
commented
Sep 19, 2024
Contributor
Author
uros-db
left a comment
uros-db
left a comment
There was a problem hiding this comment.
thanks @miland-db
here is the corresponding JIRA ticket: https://issues.apache.org/jira/browse/SPARK-49392
and the previous (original) PR: #47873
MaxGekk
approved these changes
Sep 20, 2024
Member
|
+1, LGTM. Merging to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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?
Change
sqlStateto KD010.Why are the changes needed?
Necessary modification for the Databricks error class space.
Does this PR introduce any user-facing change?
Yes, the new error message is now updated to KD010.
How was this patch tested?
Existing tests (updated).
Was this patch authored or co-authored using generative AI tooling?
No.