hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2543) No-permission-checking mode for smooth transition to 0.16's permissions features.
Date Mon, 14 Jan 2008 20:06:36 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558761#action_12558761
] 

Hairong Kuang commented on HADOOP-2543:
---------------------------------------

> How does this differ from the way that dfs.permissions=false works already? Is this a
documentation issue, or are there functional changes required?
Currently when dfs.permisssion=false, setOwner and setPermission does not check permission
either. The current proposal is that even when dfs.permission is equal to false, setOwner
and setPermission should be permission checked. This assumes the following use case for 0.16.0.
1, First dfs is upgraded to 0.16.0. Permission checking is turned off;
2. The admin changes file permissions and ownership while users run their jobs the same as
in 0.15.
3. The admin shuts down the cluster, turns on the permission checking, and brings up the cluster
again.
4. Now users' access to some data may be denied.

The proposal allows that only the admin and file owners make changes to file ownership and
permissions when permission checking is turned off.

> 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.


Mime
View raw message