You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/29 02:37:00 UTC
[jira] [Updated] (SPARK-21824) DROP TABLE should automatically
drop any dependent referential constraints or raise error.
[ https://issues.apache.org/jira/browse/SPARK-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-21824:
----------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
> DROP TABLE should automatically drop any dependent referential constraints or raise error.
> --------------------------------------------------------------------------------------------
>
> Key: SPARK-21824
> URL: https://issues.apache.org/jira/browse/SPARK-21824
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Suresh Thalamati
> Priority: Major
>
> DROP TABLE should raise error if there are any dependent referential constraints unless user specifies CASCADE CONSTRAINTS
> Syntax :
> {code:sql}
> DROP TABLE <name> [CASCADE CONSTRAINTS]
> {code}
> Hive drops the referential constraints automatically. Oracle requires user specify _CASCADE CONSTRAINTS_ clause to automatically drop the referential constraints, otherwise raises the error. Should we stick to the *Hive behavior* ?
--
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