[
https://issues.apache.org/jira/browse/HDFS-15312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149247#comment-17149247
]
Stephen O'Donnell commented on HDFS-15312:
------------------------------------------
Yes I think this change is OK (in concept, I did not do a detailed review of
the workings - just a quick look). I think the point of HDFS-10488 was that
webhdfs should not use a value inside the NN as the umask. However as I
understand it, explorer.js is just the web UI filesystem browser, and it makes
calls to webhdfs - it is picking up the configured umask and then passing the
correct "&permission=<OCTAL>" parameter to webhdfs. This leave full flexibility
with other clients using webhdfs, and therefore will not be a problem.
> 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
> Assignee: 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: [email protected]
For additional commands, e-mail: [email protected]
