[HADOOP-11347] RawLocalFileSystem#mkdir and create should honor umask

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 3.0.0-alpha1
• Component/s: fs
• Labels: BB2015-05-RFC incompatible
• Hadoop Flags: Incompatible change
• Assignee: Varun Saxena
• Reporter: Chris Nauroth
• Created: 02/Dec/14 21:29
• Updated: 25/Jan/18 22:21
• Resolved: 09/Jun/15 00:49

Description

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.

Issue Links

• breaks: MAPREDUCE-6396 TestPipeApplication fails by NullPointerException
• breaks: HADOOP-12100 ImmutableFsPermission should not override applyUmask since that method doesn't modify the FsPermission
• is related to: MAPREDUCE-7033 Map outputs implicitly rely on permissive umask for shuffle
• relates to: HADOOP-11321 copyToLocal cannot save a file to an SMB share unless the user has Full Control permissions.