[
https://issues.apache.org/jira/browse/HDFS-15312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17096374#comment-17096374
]
Stephen O'Donnell commented on HDFS-15312:
------------------------------------------
This was discussed a long time ago here:
https://issues.apache.org/jira/browse/HDFS-10488?focusedCommentId=15317387&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15317387
Then, the consensus was that webhdfs, running inside the NN is working as it
should and it should not apply the umask.
If you are creating files over webhdfs, and you want them to have a certain
permission, then you can specific the desired permission as a parameter, eg:
curl -i -X PUT "http://<HOST>:<PORT>/<PATH>?op=MKDIRS[&permission=<OCTAL>]"
> Apply umask when creating directory by WebHDFS
> ----------------------------------------------
>
> Key: HDFS-15312
> URL: https://issues.apache.org/jira/browse/HDFS-15312
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: webhdfs
> Reporter: Ye Ni
> Priority: Minor
>
> WebHDFS methods for creating file/directories were always creating it with
> 755 permissions as default for both files and directories.
> The configured *fs.permissions.umask-mode* is intentionally ignored.
> This Jira is to apply this setting in such scenario.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
