[SPARK-59437][SQL] Assign a name to the error condition _LEGACY_ERROR_TEMP_1060 - #58750
Open
Ma77Ball wants to merge 1 commit into
Open
[SPARK-59437][SQL] Assign a name to the error condition _LEGACY_ERROR_TEMP_1060#58750Ma77Ball wants to merge 1 commit into
Ma77Ball wants to merge 1 commit into
Conversation
Ma77Ball
force-pushed
the
assign-name-legacy-error-1060
branch
from
September 12, 2026 08:57
bb445ff to
77db7e7
Compare
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_1060to the named subclassUNSUPPORTED_FEATURE.NESTED_COLUMN(SQLSTATE0A000). It is raised when a command such asDESC TABLE COLUMNor JDBC filter push down is given a nested column it cannot operate on.Why are the changes needed?
The error-conditions README disallows new
_LEGACY_ERROR_TEMP_*entries and asks existing ones to be resolved. This resolves one (part of SPARK-37935).Does this PR introduce any user-facing change?
Yes. The condition becomes
UNSUPPORTED_FEATURE.NESTED_COLUMN, and the rendered message gains the standardThe feature is not supported:prefix and quotes the column with backticks, e.g.The feature is not supported: DESC TABLE COLUMN does not support nested column `col.x`.How was this patch tested?
Updated the existing
checkErrortest inDataSourceV2SQLSuiteand converted the message assertion inDescribeTableSuiteBasetocheckError.SparkThrowableSuitepasses.Was this patch authored or co-authored using generative AI tooling?
Co-authored with Claude Opus 4.8