[
https://issues.apache.org/jira/browse/SPARK-52159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Gekk resolved SPARK-52159.
------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 50835
[https://github.com/apache/spark/pull/50835]
> [JDBC] Improve error handling in table exists check
> ---------------------------------------------------
>
> Key: SPARK-52159
> URL: https://issues.apache.org/jira/browse/SPARK-52159
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 4.1.0
> Reporter: Milan Stefanovic
> Assignee: Milan Stefanovic
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> Currently JDBCTableCatalog table existence check is converting any exception
> thrown by dialect into `false`, and rethrowing as specific table not found
> exception.
>
> This results in analysis failure saying `TABLE_OR_VIEW_NOT_FOUND`. This can
> be misleading as table existence check can fail for different reasons - for
> example connection failures.
>
> `TABLE_OR_VIEW_NOT_FOUND` should be thrown only when table really does not
> exists on remote system.
>
> Proposal is to extend JDBCDialect to process exception from table existence
> check, and rethrow only if exception matches table not found exception on
> remote system.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
