hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13508) FsPermission string constructor does not recognize sticky bit
Date Thu, 01 Sep 2016 18:34:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Douglas updated HADOOP-13508:
-----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-alpha2
           Status: Resolved  (was: Patch Available)

+1

I committed this. Thanks Atul

> 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: 3.0.0-alpha2
>
>         Attachments: HADOOP-13508-1.patch, HADOOP-13508-2.patch, HADOOP-13508.003.patch,
HADOOP-13508.004.patch, HADOOP-13508.005.patch, HADOOP-13508.006.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.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message