[
https://issues.apache.org/jira/browse/HADOOP-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563320#action_12563320
]
Tsz Wo (Nicholas), SZE commented on HADOOP-2531:
------------------------------------------------
> Okay, I found it: the default permissions on upgrade are 777, with both user
> and group set to HadoopAnonymous. So I'm now leaning towards switching to
> dfs.permissions=true by default.
The information above is out-dated. The current situation is:
- dfs.permissions=*true* by default
For upgrade,
- default owner: *fsOwner*, which is the user who run NameNode
- default group: *supergroup*, which is the value set in
dfs.permissions.supergroup
- default permission: *777*
So, shell we mark this issue "won't fix"?
> HDFS FileStatus.getPermission() should return 777 when dfs.permissions=false
> ----------------------------------------------------------------------------
>
> Key: HADOOP-2531
> URL: https://issues.apache.org/jira/browse/HADOOP-2531
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Doug Cutting
>
> Generic permission checking code should still work correctly when
> dfs.permissions=false. Currently FileStatus#getPermission() returns the
> actual permission when dfs.permissions=false on the namenode, which is
> incorrect, since all accesses are permitted in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
