You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Anton Okolnychyi (Jira)" <ji...@apache.org> on 2023/06/27 22:28:00 UTC

[jira] [Updated] (SPARK-43203) Fix DROP table behavior in session catalog

     [ https://issues.apache.org/jira/browse/SPARK-43203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Okolnychyi updated SPARK-43203:
-------------------------------------
    Issue Type: Bug  (was: Improvement)

> Fix DROP table behavior in session catalog
> ------------------------------------------
>
>                 Key: SPARK-43203
>                 URL: https://issues.apache.org/jira/browse/SPARK-43203
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.4.0
>            Reporter: Anton Okolnychyi
>            Assignee: Jia Fan
>            Priority: Major
>             Fix For: 3.5.0
>
>
> DROP table behavior is not working correctly in 3.4.0 because we always invoke V1 drop logic if the identifier looks like a V1 identifier. This is a big blocker for external data sources that provide custom session catalogs.
> See [here|https://github.com/apache/spark/pull/37879/files#r1170501180] for details.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org