[ https://issues.apache.org/jira/browse/HADOOP-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578708#comment-14578708 ]
Hudson commented on HADOOP-11347: --------------------------------- FAILURE: Integrated in Hadoop-Yarn-trunk #953 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/953/]) HADOOP-11347. RawLocalFileSystem#mkdir and create should honor umask (Varun Saxena via Colin P. McCabe) (cmccabe: rev fc2ed4a1f9a19d61f5e3cb4fd843604f0c7fe95f) * hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/RawLocalFileSystem.java * hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestLocalFileSystemPermission.java * hadoop-common-project/hadoop-common/CHANGES.txt > RawLocalFileSystem#mkdir and create should honor umask > ------------------------------------------------------ > > 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, incompatible > Fix For: 3.0.0 > > Attachments: HADOOP-11347.001.patch, HADOOP-11347.002.patch, > HADOOP-11347.004.patch, HADOOP-11347.03.patch, HADOOP-11347.05.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)