[SPARK-48803][FOLLOWUP] Remove unused error-condition _LEGACY_ERROR_TEMP_2088#47783
Closed
panbingkun wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-48803][FOLLOWUP] Remove unused error-condition _LEGACY_ERROR_TEMP_2088#47783panbingkun wants to merge 1 commit intoapache:masterfrom
_LEGACY_ERROR_TEMP_2088#47783panbingkun wants to merge 1 commit intoapache:masterfrom
Conversation
Contributor
Author
MaxGekk
approved these changes
Aug 16, 2024
Member
|
+1, LGTM. Merging to master. |
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?
The pr is following up #47208.
Why are the changes needed?
In this PR #47208, the method
dataTypeUnsupportedYetErrorof using_LEGACY_ERROR_TEMP_2088has been removed, but the corresponding error condition_LEGACY_ERROR_TEMP_2088has not been synchronously deleted, and currently the Spark code repo no longer uses this error condition.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.