[
https://issues.apache.org/jira/browse/HADOOP-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558770#action_12558770
]
Doug Cutting commented on HADOOP-2543:
--------------------------------------
> 1) all files and directories will be owned by the super user and super group;
That seems fine.
> 2) the permission of the files is set to be 0600 and the permission of the
> directories is set to be 0700.
The use of dfs.permissions=false should be optional, no? Folks should be able
to upgrade and use the filesystem as before, but this would break that. The
default protection after upgrade should continue to be 777 and that folks
should need to explicitly tighten permissions rather than explicitly loosen
them.
> No-permission-checking mode for smooth transition to 0.16's permissions
> features.
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-2543
> URL: https://issues.apache.org/jira/browse/HADOOP-2543
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.15.1
> Reporter: Sanjay Radia
> Assignee: Hairong Kuang
> Fix For: 0.16.0
>
>
> In moving to 0.16, which will support permissions, a mode of no-permission
> checking has been proposed to allow smooth transition to using the new
> permissions feature.
> The idea is that at first 0.16 will be used for a period of time with
> permission checking off.
> Later after the admin has changed ownership and permissions of various files,
> the permission checking can be turned off.
> This Jira defines what the semantics are of the no-permission-checking mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
