You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2014/01/24 23:11:43 UTC
[jira] [Commented] (HADOOP-10246) define FS permissions model with
tests
[ https://issues.apache.org/jira/browse/HADOOP-10246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881474#comment-13881474 ]
Colin Patrick McCabe commented on HADOOP-10246:
-----------------------------------------------
I agree that we should have more tests for this. However, the current behavior seems correct to me. It's modelled closely on the traditional POSIX behavior, where {{mkdir}} honors {{umask}}, but {{chmod}} does not. Anything else would be surprising for users coming from traditional filesystems.
Another reason for the current behavior is that if {{chmod}} consulted {{umask}}, there would be no way for users to set less restrictive permissions than specified in {{umask}}. This is contrary to the purpose of {{umask}}, which is just to be a helpful default, not a hard constraint.
> define FS permissions model with tests
> --------------------------------------
>
> Key: HADOOP-10246
> URL: https://issues.apache.org/jira/browse/HADOOP-10246
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
> Reporter: Steve Loughran
> Priority: Minor
>
> It's interesting that HDFS mkdirs(dir, permission) uses the umask, but setPermissions() does not
> The permissions model, including umask logic should be defined and have tests implemented by those filesystems that support permissions-based security
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)