[SPARK-43539][SQL] Assign a name to the error class _LEGACY_ERROR_TEMP_0003#41200
Closed
panbingkun wants to merge 3 commits intoapache:masterfrom
Closed
[SPARK-43539][SQL] Assign a name to the error class _LEGACY_ERROR_TEMP_0003#41200panbingkun wants to merge 3 commits intoapache:masterfrom
panbingkun wants to merge 3 commits intoapache:masterfrom
Conversation
MaxGekk
requested changes
May 19, 2023
Member
MaxGekk
left a comment
MaxGekk
left a comment
There was a problem hiding this comment.
@panbingkun Could you wrap op by toSQLStmt() at:
Contributor
Author
|
This is done. |
Member
|
+1, LGTM. Merging to master. |
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?
The pr aims to assign a name to the error class _LEGACY_ERROR_TEMP_0003.
Why are the changes needed?
The changes improve the error framework.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.