[SPARK-37940][SQL]update error mechanism to fully SparkThrowable #51108
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
As stated in https://issues.apache.org/jira/browse/SPARK-37940, migrate the following errors to new error mechanism:
missingStaticPartitionColumn->MISSING_STATIC_PARTITION_COLUMN
_LEGACY_ERROR_TEMP_1045->UNSUPPORTED_FEATURE.ALTER_TABLE_SET_LOCATION_WITH_PARTITION
_LEGACY_ERROR_TEMP_1076->INVALID_PARTITION_SPEC
_LEGACY_ERROR_TEMP_1082->PARTITION_NOT_SPECIFY_LOCATION_URI
_LEGACY_ERROR_TEMP_1111->UNSUPPORTED_FEATURE.DESC_PARTITION_FOR_V2_TABLE
_LEGACY_ERROR_TEMP_1121->UNSUPPORTED_FEATURE.TABLE_MANAGEMENT
_LEGACY_ERROR_TEMP_1128->PARTITION_COLUMN_NOT_SPECIFIED
_LEGACY_ERROR_TEMP_1145->INVALID_PARTITION_COLUMN
_LEGACY_ERROR_TEMP_1146->MULTIPLE_PARTITION_COLUMN_VALUES_SPECIFIED
_LEGACY_ERROR_TEMP_1155->PARTITION_COLUMN_NOT_FOUND_IN_SCHEMA
_LEGACY_ERROR_TEMP_1163->MISMATCHED_TABLE_PARTITION_COLUMN
_LEGACY_ERROR_TEMP_1232->INVALID_PARTITION_SPEC_KEYS
Why are the changes needed?
migrate to new error mechanism.
Does this PR introduce any user-facing change?
No
How was this patch tested?
UT
Was this patch authored or co-authored using generative AI tooling?
No