[SPARK-54492][SQL] Rename _LEGACY_ERROR_TEMP_1201 and add sqlState #53197
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
|
LGTM pending CI. |
allisonwang-db
approved these changes
Nov 26, 2025
LuciferYang
previously approved these changes
Nov 26, 2025
Contributor
|
I see #53198 is also SPARK-54492, we need two different Jira tickets to track them. @aleksandr-chernousov-db |
Author
Changed other PR to SPARK-54526 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
I rename _LEGACY_ERROR_TEMP_1201 to more understandable name (UNRESOLVED_COLUMN_AMONG_FIELD_NAMES) and add sqlState
Why are the changes needed?
This is a frequent error that is not classified
Does this PR introduce any user-facing change?
No
How was this patch tested?
This is a small refactoring, tests are already there
Was this patch authored or co-authored using generative AI tooling?
No