[
https://issues.apache.org/jira/browse/HIVE-11418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968168#comment-15968168
]
Sergio Peña commented on HIVE-11418:
------------------------------------
The PURGE does not exist on the DROP DATABASE yet. We were thinking if adding
it on branch-2 in order to delete an encrypted table without sending it to
trash as this patch with hadoop 2.8 will work only on 3.0.
The current workaround is to delete one table at a time when they're encrypted
and trash is enabled. So one option (if we don't want to include PURGE then
remove it on 3.0) is to mark it as a known bug on Hive versions older than 3.0.
Does it make sense?
> 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)
