[
https://issues.apache.org/jira/browse/HIVE-11418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959608#comment-15959608
]
Sahil Takiar commented on HIVE-11418:
-------------------------------------
Support for Trash + Encryption Zones was added in HDFS by HDFS-8831
{{HiveMetaStore}} also has a check to see if trash + encryption zones are
enabled for a table, if they are then it will throw the exception above.
If we can pickup HDFS-8831 (Hadoop 2.8.0) and remove the check in
{{HiveMetaStore}}, then we should be able to get around this.
> 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
>
> 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)