You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2017/02/13 19:06:41 UTC
[jira] [Commented] (HADOOP-13508) FsPermission string constructor
does not recognize sticky bit
[ https://issues.apache.org/jira/browse/HADOOP-13508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864225#comment-15864225 ]
Wei-Chiu Chuang commented on HADOOP-13508:
------------------------------------------
Pushed the commit into branch-2.8
> FsPermission string constructor does not recognize sticky bit
> -------------------------------------------------------------
>
> Key: HADOOP-13508
> URL: https://issues.apache.org/jira/browse/HADOOP-13508
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Atul Sikaria
> Assignee: Atul Sikaria
> Fix For: 2.9.0, 3.0.0-alpha2, 2.8.1
>
> Attachments: HADOOP-13508.003.patch, HADOOP-13508.004.patch, HADOOP-13508.005.patch, HADOOP-13508.006.patch, HADOOP-13508-1.patch, HADOOP-13508-2.patch, HADOOP-13508.branch-2.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org