[ https://issues.apache.org/jira/browse/HADOOP-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572297#comment-14572297 ]
Varun Saxena commented on HADOOP-11347: --------------------------------------- [~cmccabe], kindly review > 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 > Affects Versions: 2.7.0 > Reporter: Chris Nauroth > Assignee: Varun Saxena > Labels: BB2015-05-RFC > Attachments: HADOOP-11347.001.patch, HADOOP-11347.002.patch, > HADOOP-11347.004.patch, HADOOP-11347.03.patch > > > 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)