You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2020/10/08 05:30:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Wenchen Fan resolved SPARK-33074.
---------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

Issue resolved by pull request 29952
[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: Sub-task
>          Components: SQL
>    Affects Versions: 3.1.0
>            Reporter: Maxim Gekk
>            Assignee: Maxim Gekk
>            Priority: Major
>             Fix For: 3.1.0
>
>
> 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