[HADOOP-6234] Permission configuration files should use octal and symbolic

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.0
• Hadoop Flags: Reviewed
• Release Note: New configuration option dfs.umaskmode sets umask with octal or symbolic value.
• Assignee: Jakob Homan
• Reporter: Allen Wittenauer
• Created: 28/Jul/08 21:05
• Updated: 26/Aug/12 04:42
• Resolved: 08/Sep/09 19:09

Description

Currently, the settings for the default umask in Hadoop configuration files require the input format be in decimal. Considering that every admin in the world thinks of permissions in octal and/or symbolic format, the config files should really use those two formats and drop decimal.

[... and, yes, I'm aware this breaks backwards compatibility. But in this case, I think that is perfectly acceptable.]

Issue Links

• blocks: HDFS-595 FsPermission tests need to be updated for new octal configuration parameter from HADOOP-6234
• is blocked by: HADOOP-6521 FsPermission:SetUMask not updated to use new-style umask setting.
• is related to: HADOOP-8727 Gracefully deprecate dfs.umaskmode in 2.x onwards
• is related to: HADOOP-6105 Provide a way to automatically handle backward compatibility of deprecated keys
• relates to: HDFS-760 "fs -put" fails if dfs.umask is set to 63
• relates to: HADOOP-6246 Update umask code to use key deprecation facilities from HADOOP-6105