[HADOOP-13508] FsPermission string constructor does not recognize sticky bit

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-alpha2, 2.8.2, 2.7.6
• Target Version/s: 2.9.0, 3.0.0-alpha1
• Hadoop Flags: Reviewed
• Assignee: Atul Sikaria
• Reporter: Atul Sikaria
• Created: 17/Aug/16 20:53
• Updated: 19/Jan/18 01:12
• Resolved: 15/Dec/16 21:53

Description

FsPermissions's string constructor breaks on valid permission strings, like "1777".

This is because FsPermission class naïvely uses UmaskParser to do it’s parsing of permissions: (from source code):
public FsPermission(String mode) {
this((new UmaskParser(mode)).getUMask());
}

The mode string UMask accepts is subtly different (esp wrt sticky bit), so parsing Umask is not the same as parsing FsPermission.

Issue Links

• is required by: HDFS-11084 Add a regression test for sticky bit support of OIV ReverseXML processor