You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/06/20 00:18:22 UTC
[jira] [Commented] (HDFS-4919) Improve documentation of
dfs.permissions.enabled flag.
[ https://issues.apache.org/jira/browse/HDFS-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688546#comment-13688546 ]
Colin Patrick McCabe commented on HDFS-4919:
--------------------------------------------
Do we still need this flag in hadoop-2 and beyond? The documentation implies that part of having it was to "allow administrators to reliably set owners and permissions in advance of turning on regular permissions checking." Surely everyone who needed to do this conversion process has already done so since hadoop 0.22. I don't know of anyone who would use this flag nowadays, even developers.
> Improve documentation of dfs.permissions.enabled flag.
> ------------------------------------------------------
>
> Key: HDFS-4919
> URL: https://issues.apache.org/jira/browse/HDFS-4919
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Chris Nauroth
>
> The description of dfs.permissions.enabled in hdfs-default.xml does not state that permissions are always checked on certain calls regardless of this configuration. The HDFS permissions guide still mentions the deprecated dfs.permissions property instead of the currently supported dfs.permissions.enabled.
> http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsPermissionsGuide.html#Configuration_Parameters
--
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