hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-10978) Document fs.trash.interval wrt Hive and HDFS Encryption
Date Fri, 28 Aug 2015 05:37:45 GMT


Lefty Leverenz commented on HIVE-10978:

This can be documented in the AdminManual Configuration section "Hive Configuration Variables
Used to Interact with Hadoop" -- fs.trash.interval belongs in the table of configs, and for
extra visibility a small subsection could be added after the table.

* [Hive Configuration Variables Used to Interact with Hadoop |]

By the way, the section title "Hive Configuration Variables ..." is misleading since none
of them are hive.* variables, so I recommend changing it to "Other Configuration Variables
..." or some such.

> Document fs.trash.interval wrt Hive and HDFS Encryption
> -------------------------------------------------------
>                 Key: HIVE-10978
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Documentation, Security
>    Affects Versions: 1.2.0
>            Reporter: Eugene Koifman
>            Priority: Critical
>              Labels: TODOC1.2
> This should be documented in 1.2.1 Release Notes
> When HDFS is encrypted (TDE is enabled), DROP TABLE and DROP PARTITION have unexpected
behavior when Hadoop Trash feature is enabled.
> The later is enabled by setting fs.trash.interval > 0 in core-site.xml.
> When Trash is enabled, the data file for the table, should be "moved" to Trash bin. If
the table is inside an Encryption Zone, this "move" operation is not allowed.
> There are 2 ways to deal with this:
> 1. use PURGE, as in DROP TABLE blah PURGE. This skips the Trash bin even if enabled.
> 2. set fs.trash.interval = 0. It is critical that this config change is done in core-site.xml.
Setting it in hive-site.xml may lead to very strange behavior where the table metadata is
deleted but the data file remains.  This will lead to data corruption if a table with the
same name is later created.

This message was sent by Atlassian JIRA

View raw message