-
Notifications
You must be signed in to change notification settings - Fork 28.6k
[SPARK-46608][SQL] Restore backward compatibility of JdbcDialect.classifyException
#44449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
0736218
Restore backward compatibility of JdbcDialect.classifyException
MaxGekk a1568c6
Add the error sub-class: FAILED_JDBC.UNCLASSIFIED
MaxGekk 1138304
Fix JDBCV2Suite
MaxGekk 4ddef49
Fix JDBCTableCatalogSuite
MaxGekk 1323be5
AnalysisException -> SparkException
MaxGekk dc1d452
Change the integration tests
MaxGekk aff9479
Fix imports
MaxGekk d0ea469
Fix tests
MaxGekk d6c29a6
Fix integration tests
MaxGekk 11be4fe
Implement alternative approach
MaxGekk 58d7e99
Merge remote-tracking branch 'origin/master' into restore-jdbc-classi…
MaxGekk 38b701f
Re-gen .md
MaxGekk 814ce3c
Fix tests
MaxGekk 0cfce60
Fix tests
MaxGekk aae4089
Fix tests
MaxGekk a0a27e1
Deprecate old classifyException
MaxGekk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of passing
description
around, shall we generate the description here using the error class name and thetableName
in the parameters?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be not fully compatible with existing JDBC dialects because values in
messageParameters
has been preprocessed already like quoting, and a JDBC dialect could use regexp for parsing parameters frommessage
/description
. Theoretically, it can break the regexps.And if we pass the quoting values to an JDBC dialect, it can throw some Spark exception which performs quoting inside like
PostgresDialect
throwsNonEmptyNamespaceException
. The last one does quoting inside its constructor. Apparently, we will get double quoting values which is a bug already.