You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Andy Isaacson (JIRA)" <ji...@apache.org> on 2013/01/24 21:53:14 UTC
[jira] [Created] (HDFS-4439) umask-mode does not support 4-digit
umask value
Andy Isaacson created HDFS-4439:
-----------------------------------
Summary: 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
Reporter: Andy Isaacson
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira