[HDFS-4439] umask-mode does not support 4-digit umask value

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.0-alpha1
• Component/s: hdfs-client
• Assignee: Chu Tong
• Reporter: Andy Isaacson
• Created: 24/Jan/13 20:51
• Updated: 21/Nov/16 12:51
• Resolved: 21/Nov/16 12:31

Description

Best practice for specifying file permissions using the legacy octal format is to always add a leading "0" to ensure the value is treated as octal. However the fs.permissions.umask-mode parsing code throws an error when given a 4-digit string:

$ hdfs dfs -Dfs.permissions.umask-mode=0000 -touchz foo.txt
2013-01-24 12:49:02,352 WARN  permission.FsPermission (FsPermission.java:getUMask(245)) - Unable to parse configuration fs.permissions.umask-mode with value 0000 as octal or symbolic umask.
-touchz: Unable to parse configuration fs.permissions.umask-mode with value 0000 as octal or symbolic umask.
Usage: hadoop fs [generic options] -touchz <path> ...

There's no downside to supporting 0000, so hdfs should handle it gracefully.

Issue Links

• is duplicated by: HADOOP-10945 4-digit octal umask permissions throws a parse error