You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Reuben Kuhnert (JIRA)" <ji...@apache.org> on 2015/04/14 19:17:12 UTC

[jira] [Assigned] (HIVE-6754) Inconsistent default for hive.exec.drop.ignorenonexistent

     [ https://issues.apache.org/jira/browse/HIVE-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reuben Kuhnert reassigned HIVE-6754:
------------------------------------

    Assignee: Reuben Kuhnert

> 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)