[
https://issues.apache.org/jira/browse/HDFS-10488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318433#comment-15318433
]
Wellington Chevreuil commented on HDFS-10488:
---------------------------------------------
Thanks for the suggestions, [~jojochuang] and [~cnauroth] for the detailed
explanation. I was going to upload another patch with pointers made by
[~jojochuang], then I saw [~cnauroth] comments.
So, [~cnauroth], summarizing, *fs.permissions.umask-mode* should not be applied
for WebHDFS created directories/files. I think the explained intentions behind
this is not clear on the documentation, so yes, I would like to work on a
documentation patch for this.
Additional points:
1) While working on this, I had found out the default permission (if no
permission is specified while calling the method) for both directories and
files created by WebHDFS currently is *755*. However, defining "execution"
permissions for HDFS files don't have any value. Should this be changed to give
different default permissions for files and directories?
2) Still on the default values, setting *755* as default can lead to confusion
about umask being used. Since default umask is *022*, users can conclude that
the umask is being applied when they see newly created directories got *755*.
Should this be changed to more permissive permissions such as *777*?
3) When working on tests for WebHDFS CREATESYMLINK as suggested by
[~jojochuang], I realized this method is no longer supported. Should we simply
remove from WebHDFS, or only document this is not supported anymore and leave
it giving the current error?
> 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
> Affects Versions: 2.6.0
> Reporter: Wellington Chevreuil
> Priority: Minor
> Attachments: HDFS-10488.002.patch, HDFS-10488.003.patch,
> HDFS-10488.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
