hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-4487) Hive does not set explicit permissions on hive.exec.scratchdir
Date Tue, 24 Feb 2015 09:00:11 GMT


Lefty Leverenz commented on HIVE-4487:

Doc note:  This adds configuration parameter *hive.scratch.dir.permission* to,
so it needs to be documented in the wiki (in two places):

* [AdminManual Configuration -- Configuration Variables |]
* [Configuration Properties -- put it after hive.exec.scratchdir |]

HIVE-6847 adds a parameter description in release 0.14.0.

> Hive does not set explicit permissions on hive.exec.scratchdir
> --------------------------------------------------------------
>                 Key: HIVE-4487
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Joey Echeverria
>            Assignee: Chaoyu Tang
>              Labels: TODOC12
>             Fix For: 0.12.0
>         Attachments: HIVE-4487.patch
> The hive.exec.scratchdir defaults to /tmp/hive-$\{\}, but when Hive creates
this directory it doesn't set any explicit permission on it. This means if you have the default
HDFS umask setting of 022, then these directories end up being world readable. These permissions
also get applied to the staging directories and their files, thus leaving inter-stage data
world readable.
> This can cause a potential leak of data especially when operating on a Kerberos enabled
cluster. Hive should probably default these directories to only be readable by the owner.

This message was sent by Atlassian JIRA

View raw message