[
https://issues.apache.org/jira/browse/HIVE-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771952#comment-13771952
]
Brock Noland commented on HIVE-4487:
------------------------------------
Very strange. I don't see why this would be occurring since the hiveptest owns
everything in /home/hiveptest/. It's not a privileged user so cannot it cannot
change ownership. The only way I can see that is if
"hive_2013-09-18_19-22-30_852_799993877859563099-1" somehow got created with
000 (or anything but 700).
> Hive does not set explicit permissions on hive.exec.scratchdir
> --------------------------------------------------------------
>
> Key: HIVE-4487
> URL: https://issues.apache.org/jira/browse/HIVE-4487
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Joey Echeverria
> Assignee: Chaoyu Tang
> Fix For: 0.12.0
>
> Attachments: HIVE-4487.patch
>
>
> The hive.exec.scratchdir defaults to /tmp/hive-$\{user.name\}, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
