hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10945) 4-digit octal umask permissions throws a parse error
Date Thu, 07 Aug 2014 16:26:14 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089401#comment-14089401
] 

Jason Lowe commented on HADOOP-10945:
-------------------------------------

Example failure:

{noformat}
$ hadoop fs -Dfs.permissions.umask-mode=0022 -ls
2014-08-07 16:10:27,811 WARN  [main] permission.FsPermission (FsPermission.java:getUMask(260))
- Unable to parse configuration fs.permissions.umask-mode with value 0022 as octal or symbolic
umask.
-ls: Unable to parse configuration fs.permissions.umask-mode with value 0022 as octal or symbolic
umask.
Usage: hadoop fs [generic options] -ls [-d] [-h] [-R] [<path> ...]
{noformat}

The pattern match for a valid octal pattern in UmaskParser probably needs to look a little
more like the one from ChmodParser.  I realize that the umask can't specify the sticky bit,
but we shouldn't preclude an equivalent number to a valid umask.

> 4-digit octal umask permissions throws a parse error
> ----------------------------------------------------
>
>                 Key: HADOOP-10945
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10945
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.2.0
>            Reporter: Jason Lowe
>
> Providing a 4-digit octal number for fs permissions leads to a parse error, e.g.: -Dfs.permissions.umask-mode=0022



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message