Suresh Thalamati created SPARK-21824: ----------------------------------------
Summary: 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.0.0 Reporter: Suresh Thalamati 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org