yuexing opened a new pull request, #51108:
URL: https://github.com/apache/spark/pull/51108
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
