[HIVE-6754] Inconsistent default for hive.exec.drop.ignorenonexistent

• Type: Bug
• Status: Patch Available
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 0.12.0
• Component/s: Configuration
• Assignee: Reuben Kuhnert
• Reporter: Natalino Busa
• Created: 26/Mar/14 10:00
• Updated: 04/May/15 21:22

Description

Dropping a non existing table returns no errors

• when IF EXISTS is added
• when hive.exec.drop.ignorenonexistent is set to true

The default configuration in hive-default.xml.template sets hive.exec.drop.ignorenonexistent to true.

However this create a inconsistent default behaviour when DROP TABLE is executed on a non existing table, when the if exists clause is not used.

My suggestion would be to have the default set to false, to align the behavior to the way it's used in SQL.

Issue Links

• relates to: HIVE-9638 Drop Index does not check Index or Table exisit or not
• relates to: HIVE-1856 Implement DROP TABLE/VIEW ... IF EXISTS