[SPARK-45487] Fix SQLSTATEs and temp errors #43342
Closed
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
srielau
changed the title
srielau
force-pushed
the
SPARK-45487-Fix-temp-errors
branch
from
40cd83d to
afb7547
Compare
Contributor
Author
|
@MaxGekk Can you review? I will follow up with a couple more to get through all the SQLSTATEs. |
srielau
changed the title
gengliangwang
approved these changes
Oct 13, 2023
Member
|
Thanks, merging to master |
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 replaces TEMP error message 3007 and fills in many missing SQLSTATEs.
Why are the changes needed?
This is part of the ongoing effort to switch to the new error framework.
Does this PR introduce any user-facing change?
yes, error docs will now show more SQLSTATEs
How was this patch tested?
Existing QA suite was run.
Was this patch authored or co-authored using generative AI tooling?
No