[
https://issues.apache.org/jira/browse/SPARK-43203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Okolnychyi updated SPARK-43203:
-------------------------------------
Description:
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.
was:
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
blockers for external data sources that provide custom session catalogs.
See [here|https://github.com/apache/spark/pull/37879/files#r1170501180] for
details.
> Fix DROP table behavior in session catalog
> ------------------------------------------
>
> Key: SPARK-43203
> URL: https://issues.apache.org/jira/browse/SPARK-43203
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.4.0
> Reporter: Anton Okolnychyi
> Priority: Major
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
