[
https://issues.apache.org/jira/browse/HIVE-11418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964492#comment-15964492
]
Sergio Peña commented on HIVE-11418:
------------------------------------
+1
The patch looks good [~stakiar].
Regarding branch-2, yes we should fix it, but I don't know if adding a PURGE
keyword to the DROP DATABASE would be ideal now that we know Hadoop 2.8 fixes
this.
[~ashutoshc] What do you think on adding the PURGE keyword on DROP DATABASE?
Would this be useful on Hive to avoid sending the whole DB to the trash?
> Dropping a database in an encryption zone with CASCADE and trash enabled fails
> ------------------------------------------------------------------------------
>
> Key: HIVE-11418
> URL: https://issues.apache.org/jira/browse/HIVE-11418
> Project: Hive
> Issue Type: Sub-task
> Affects Versions: 1.2.0
> Reporter: Sergio Peña
> Assignee: Sahil Takiar
> Attachments: HIVE-11418.1.patch, HIVE-11418.2.patch
>
>
> Here's the query that fails:
> {noformat}
> hive> CREATE DATABASE db;
> hive> USE db;
> hive> CREATE TABLE a(id int);
> hive> SET fs.trash.interval=1;
> hive> DROP DATABASE db CASCADE;
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Unable to drop
> db.a because it is in an encryption zone and trash
> is enabled. Use PURGE option to skip trash.)
> {noformat}
> DROP DATABASE does not support PURGE, so we have to remove the tables one by
> one, and then drop the database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
