[SPARK-50248][SQL] Assign appropriate error condition for _LEGACY_ERROR_TEMP_2058: INVALID_PARTITION_VALUE
#48778
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
…OR_TEMP_2058: INVALID_PARTITION_COLUMN_CAST
MaxGekk
reviewed
Nov 7, 2024
MaxGekk
changed the title
_LEGACY_ERROR_TEMP_2058: INVALID_PARTITION_COLUMN_CAST_LEGACY_ERROR_TEMP_2058: INVALID_PARTITION_VALUE
MaxGekk
approved these changes
Nov 13, 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
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 proposes to Integrate
_LEGACY_ERROR_TEMP_2058intoINVALID_PARTITION_VALUEWhy are the changes needed?
To improve the error message by assigning proper error condition and SQLSTATE
Does this PR introduce any user-facing change?
No, only user-facing error message improved
How was this patch tested?
Updated the existing tests
Was this patch authored or co-authored using generative AI tooling?
No