[SPARK-55862][SQL] Rename _LEGACY_ERROR_TEMP_2027 to UNEXPECTED_OPERATOR_IN_CORRELATED_SUBQUERY#54656
Open
mikhailnik-db wants to merge 1 commit intoapache:masterfrom
Conversation
…ATED_SUBQUERY Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
mikhailnik-db
changed the title
mikhailnik-db
changed the title
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?
Rename the legacy error condition
_LEGACY_ERROR_TEMP_2027to a proper error classUNEXPECTED_OPERATOR_IN_CORRELATED_SUBQUERYwith SQL state0A000(feature not supported).Why are the changes needed?
_LEGACY_ERROR_TEMP_2027is a legacy placeholder error name. It should be replaced with a descriptive error class name and assigned a proper SQL state to improve error reporting and comply with the ANSI SQL standard.Does this PR introduce any user-facing change?
Yes. The error condition name changes from
_LEGACY_ERROR_TEMP_2027toUNEXPECTED_OPERATOR_IN_CORRELATED_SUBQUERYand now includes SQL state0A000. The error message itself remains unchanged.How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code 2.1.70