[SPARK-55812][SQL] Consolidate dataSchemaNotSpecifiedError to use UNABLE_TO_INFER_SCHEMA#54591
Open
miland-db wants to merge 1 commit intoapache:masterfrom
Open
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
1 participant
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 consolidates the 2-parameter overload of
dataSchemaNotSpecifiedErrorto use the existingUNABLE_TO_INFER_SCHEMAerror class (SQL state42KD9).Changes:
dataSchemaNotSpecifiedError()method to delegate to the 1-parameter version_LEGACY_ERROR_TEMP_1134fromerror-conditions.jsonPreviously, the 2-parameter overload used
_LEGACY_ERROR_TEMP_1134with no SQL state, while the 1-parameter version already usedUNABLE_TO_INFER_SCHEMAwith SQL state42KD9.Why are the changes needed?
This is needed to ensure reliable error reporting.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
The 1-parameter version already has comprehensive test coverage via
UNABLE_TO_INFER_SCHEMA.Was this patch authored or co-authored using generative AI tooling?
No.