[SPARK-55813][SQL] Rename _LEGACY_ERROR_TEMP_2078 to JDBC_TABLE_AND_QUERY_BOTH_SPECIFIED with SQL state 42000#54592
Open
miland-db wants to merge 1 commit intoapache:masterfrom
Conversation
srielau
approved these changes
Mar 4, 2026
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?
This PR adds a proper error class and SQL state for the
cannotSpecifyBothJdbcTableNameAndQueryErrorexception.Changes:
JDBC_TABLE_AND_QUERY_BOTH_SPECIFIEDerror class to error-conditions.json with SQL state42000QueryExecutionErrors.cannotSpecifyBothJdbcTableNameAndQueryError()to use the new error class_LEGACY_ERROR_TEMP_2078legacy error classWhy are the changes needed?
Previously, this error used
_LEGACY_ERROR_TEMP_2078without a SQL state, making it harder to identify and handle programmatically in error monitoring systems.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Updated tests in
JDBCSuite.scalaWas this patch authored or co-authored using generative AI tooling?
No.