[
https://issues.apache.org/jira/browse/HADOOP-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232168#comment-14232168
]
Chris Nauroth commented on HADOOP-11347:
----------------------------------------
More details are in this comment from HADOOP-11321:
https://issues.apache.org/jira/browse/HADOOP-11321?focusedCommentId=14230778&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14230778
Note that this issue is targeted to 3.0.0. I don't believe we can change the
behavior safely on the 2.x line. Applications may be relying on the existing
behavior of {{FileSystem}}.
> Inconsistent enforcement of umask between FileSystem and FileContext
> interacting with local file system.
> --------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11347
> URL: https://issues.apache.org/jira/browse/HADOOP-11347
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Chris Nauroth
>
> The {{FileSystem}} and {{FileContext}} APIs are inconsistent in enforcement
> of umask for newly created directories. {{FileContext}} utilizes
> configuration property {{fs.permissions.umask-mode}} and runs a separate
> {{chmod}} call to guarantee bypassing the process umask. This is the
> expected behavior for Hadoop as discussed in the documentation of
> {{fs.permissions.umask-mode}}. For the equivalent {{FileSystem}} APIs, it
> does not use {{fs.permissions.umask-mode}}. Instead, the permissions end up
> getting controlled by the process umask.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
