[SPARK-43346][SQL] Change error class _LEGACY_ERROR_TEMP_1206 to COLUMN_NOT_DEFINED#41056
Closed
JinHelin404 wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-43346][SQL] Change error class _LEGACY_ERROR_TEMP_1206 to COLUMN_NOT_DEFINED#41056JinHelin404 wants to merge 1 commit intoapache:masterfrom
JinHelin404 wants to merge 1 commit intoapache:masterfrom
Conversation
JinHelin404
changed the title
JinHelin404
changed the title
Member
|
@JinHelin404 Sorry, this is a duplicate of #41020. cc @imback82 |
Contributor
Author
|
@MaxGekk Ok, i will close this pr. |
Member
|
@JinHelin404 Thank you. |
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?
In the PR, I propose to assign the proper name COLUMN_NOT_DEFINED to the legacy error class _LEGACY_ERROR_TEMP_1206.
Why are the changes needed?
see SPARK-43346
Does this PR introduce any user-facing change?
No.
How was this patch tested?
existing tests.