[SPARK-21824] DROP TABLE should automatically drop any dependent referential constraints or raise error.

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.0
• Component/s: SQL
• Assignee: Unassigned
• Reporter: Suresh Thalamati
• Created: 24/Aug/17 07:22
• Updated: 29/Mar/20 02:36

Description

DROP TABLE should raise error if there are any dependent referential constraints unless user specifies CASCADE CONSTRAINTS

Syntax :

DROP TABLE <name> [CASCADE CONSTRAINTS]

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 ?

Issue Links

• is blocked by: SPARK-21784 Add ALTER TABLE ADD CONSTRANT DDL to support defining primary key and foreign keys