Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.7.0
-
None
-
Reviewed
-
Backwards-compatible DROP behavior is controlled via new configuration parameter hive.exec.drop.ignorenonexistent
Description
This issue combines issues HIVE-1550/1165/1542/1551:
- augment DROP TABLE/VIEW with IF EXISTS
- signal an error if the table/view doesn't exist and IF EXISTS wasn't specified
- introduce a flag in the configuration that allows you to turn off the new behavior
Attachments
Attachments
Issue Links
- blocks
-
HIVE-1858 Implement DROP {PARTITION, INDEX, TEMPORARY FUNCTION} IF EXISTS
-
- Closed
-
- incorporates
-
HIVE-1542 DROP TABLE <tablename> should raise an error when <tablename> does not exist
-
- Open
-
-
HIVE-1551 DROP VIEW should raise an error if the view does not exist
-
- Resolved
-
-
HIVE-1550 Implement DROP VIEW IF EXISTS
-
- Resolved
-
-
HIVE-1165 Support `DROP TABLE XXX IF EXISTS`
-
- Resolved
-
- is duplicated by
-
HIVE-1550 Implement DROP VIEW IF EXISTS
-
- Resolved
-
- is related to
-
HIVE-6754 Inconsistent default for hive.exec.drop.ignorenonexistent
-
- Patch Available
-