[ https://issues.apache.org/jira/browse/HIVE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reuben Kuhnert updated HIVE-6754: --------------------------------- Attachment: (was: HIVE-6754.01.patch) > Inconsistent default for hive.exec.drop.ignorenonexistent > ---------------------------------------------------------- > > Key: HIVE-6754 > URL: https://issues.apache.org/jira/browse/HIVE-6754 > Project: Hive > Issue Type: Bug > Components: Configuration > Affects Versions: 0.12.0 > Reporter: Natalino Busa > Assignee: Reuben Kuhnert > Priority: Trivial > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)