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 "Wellington Chevreuil (JIRA)" <ji...@apache.org> on 2016/06/05 15:14:59 UTC
[jira] [Created] (HDFS-10488) WebHDFS CREATE and MKDIRS does not
follow same rules as DFS CLI when creating files/directories without
specifying permissions
Wellington Chevreuil created HDFS-10488:
-------------------------------------------
Summary: WebHDFS CREATE and MKDIRS does not follow same rules as DFS CLI when creating files/directories without specifying permissions
Key: HDFS-10488
URL: https://issues.apache.org/jira/browse/HDFS-10488
Project: Hadoop HDFS
Issue Type: Bug
Components: webhdfs
Reporter: Wellington Chevreuil
Priority: Minor
WebHDFS methods for creating file/directories are always creating it with 755 permissions as default, even ignoring any configured *fs.permissions.umask-mode* in the case of directories.
Dfs CLI, however, applies the configured umask to 777 permission for directories, or 666 permission for files.
Example below shows the different behaviour when creating directory via CLI and WebHDFS:
{noformat}
1) Creating a directory under '/test/' as 'test-user'. Configured fs.permissions.umask-mode is 000:
$ sudo -u test-user hdfs dfs -mkdir /test/test-user1
$ sudo -u test-user hdfs dfs -getfacl /test/test-user1
# file: /test/test-user1
# owner: test-user
# group: supergroup
user::rwx
group::rwx
other::rwx
4) Doing the same via WebHDFS does not get the proper ACLs:
$ curl -i -X PUT "http://namenode-host:50070/webhdfs/v1/test/test-user2?user.name=test-user&op=MKDIRS"
$ sudo -u test-user hdfs dfs -getfacl /test/test-user2
# file: /test/test-user2
# owner: test-user
# group: supergroup
user::rwx
group::r-x
other::r-x
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org