[
https://issues.apache.org/jira/browse/HIVE-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti updated HIVE-7001:
----------------------------------
Attachment: TestUMask.patch
Hi [~thejas], One question regarding the "fs.permissions.umask-mode". Looks
like "fs.permissions.umask-mode" doesn't exist in Hadoop 1.x and property
"dfs.umaskmode" is used instead in 1.x for the same purpose. Also
"dfs.umaskmode" was not deprecated in 1.x according to HADOOP-8727. Should we
use FsPermission.UMASK_LABEL instead of "fs.permissions.umask-mode" which
always points to proper property in latest Hadoop in each version (0.23.x, 1.x,
2.x)?
Attached a testcase to illustrate the problem. Test passes fine with
-Phadoop-2, but not with -Phadoop-1.
> fs.permissions.umask-mode is getting unset when Session is started
> ------------------------------------------------------------------
>
> Key: HIVE-7001
> URL: https://issues.apache.org/jira/browse/HIVE-7001
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.13.0
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Fix For: 0.14.0, 0.13.1
>
> Attachments: HIVE-7001.1.patch, HIVE-7001.2.patch, HIVE-7001.3.patch,
> TestUMask.patch
>
>
> {code}
> hive> set fs.permissions.umask-mode;
> fs.permissions.umask-mode=022
> hive> show tables;
> OK
> t1
> Time taken: 0.301 seconds, Fetched: 1 row(s)
> hive> set fs.permissions.umask-mode;
> fs.permissions.umask-mode is undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
