hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <>
Subject [jira] [Commented] (HIVE-6754) Inconsistent default for hive.exec.drop.ignorenonexistent
Date Mon, 04 May 2015 21:23:08 GMT


Sergio Peña commented on HIVE-6754:

Tests are failing because developers usually add a 'DROP TABLE <table>' to the tests
even if the <table> does not exist. So, this patch is causing them to fail.

Also, users might be using the same statement without IF EXISTS keywords on their scripts,
so this patch will cause errors on them as well. This is a user experience issue, so we need
to think about this solution carefully.

[~szehon] [~xuefuz] Could you help me here? 
Would we want cause errors when dropping a table that does not exist?

> Inconsistent default for  hive.exec.drop.ignorenonexistent
> ----------------------------------------------------------
>                 Key: HIVE-6754
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 0.12.0
>            Reporter: Natalino Busa
>            Assignee: Reuben Kuhnert
>            Priority: Trivial
>         Attachments: HIVE-6754.01.patch
> 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

View raw message