[
https://issues.apache.org/jira/browse/HDFS-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683461#comment-15683461
]
Brahma Reddy Battula edited comment on HDFS-4439 at 11/21/16 12:51 PM:
-----------------------------------------------------------------------
Marking as duplicate, as it's duplicated by HDFS-10945 and there is no commit
happened with this jira id.
was (Author: brahmareddy):
Marking as duplicate, as it's duplicated by HDFS-10945 and there is not commit
happened with this jira id.
> umask-mode does not support 4-digit umask value
> -----------------------------------------------
>
> Key: HDFS-4439
> URL: https://issues.apache.org/jira/browse/HDFS-4439
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 3.0.0-alpha1
> Reporter: Andy Isaacson
> Assignee: Chu Tong
> Attachments: HDFS-4439.patch
>
>
> Best practice for specifying file permissions using the legacy octal format
> is to always add a leading "0" to ensure the value is treated as octal.
> However the {{fs.permissions.umask-mode}} parsing code throws an error when
> given a 4-digit string:
> {code}
> $ hdfs dfs -Dfs.permissions.umask-mode=0000 -touchz foo.txt
> 2013-01-24 12:49:02,352 WARN permission.FsPermission
> (FsPermission.java:getUMask(245)) - Unable to parse configuration
> fs.permissions.umask-mode with value 0000 as octal or symbolic umask.
> -touchz: Unable to parse configuration fs.permissions.umask-mode with value
> 0000 as octal or symbolic umask.
> Usage: hadoop fs [generic options] -touchz <path> ...
> {code}
> There's no downside to supporting {{0000}}, so hdfs should handle it
> gracefully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
