-
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:
-
Hadoop Flags:Incompatible change
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.
- breaks
-
MAPREDUCE-6396 TestPipeApplication fails by NullPointerException
-
- Resolved
-
-
HADOOP-12100 ImmutableFsPermission should not override applyUmask since that method doesn't modify the FsPermission
-
- Closed
-
- is related to
-
MAPREDUCE-7033 Map outputs implicitly rely on permissive umask for shuffle
-
- Resolved
-
- relates to
-
HADOOP-11321 copyToLocal cannot save a file to an SMB share unless the user has Full Control permissions.
-
- Closed
-