You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2020/10/06 08:36:00 UTC
[jira] [Commented] (SPARK-33074) Classify dialect exceptions in
JDBC v2 Table Catalog
[ https://issues.apache.org/jira/browse/SPARK-33074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208566#comment-17208566 ]
Apache Spark commented on SPARK-33074:
--------------------------------------
User 'MaxGekk' has created a pull request for this issue:
https://github.com/apache/spark/pull/29952
> Classify dialect exceptions in JDBC v2 Table Catalog
> ----------------------------------------------------
>
> Key: SPARK-33074
> URL: https://issues.apache.org/jira/browse/SPARK-33074
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Maxim Gekk
> Priority: Major
>
> The current implementation of v2.jdbc.JDBCTableCatalog don't care of exceptions defined by org.apache.spark.sql.connector.catalog.TableCatalog at all like
> * NoSuchNamespaceException
> * NoSuchTableException
> * TableAlreadyExistsException
> it either throw dialect exception or generic exception AnalysisException.
> Since we split forming of dialect specific statements and their execution, we should extend dialect APIs and ask them how to convert their exceptions to TableCatalog exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org