hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2552) enable hdfs permission checking by default
Date Tue, 08 Jan 2008 20:56:34 GMT

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

Raghu Angadi commented on HADOOP-2552:
--------------------------------------

+1. Better to iron out issues earlier than later.

> enable hdfs permission checking by default
> ------------------------------------------
>
>                 Key: HADOOP-2552
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2552
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Doug Cutting
>             Fix For: 0.16.0
>
>
> We should enable permission checking in dfs by default.  Currently, on upgrade, all file
permissions are 777, so this is a back-compatible change.  After an upgrade folks can change
owners and groups and limit permissions, and things will work as expected.
> The current default, dfs.permissions=false, gives inconsistent behaviour: permissions
are displayed in 'ls' and returned by the FileSystem APIs, but they're not enforced.  In future
releases we will certainly want dfs.permissions=true to be the default, and making it so now
will thus also avoid an incompatible change.
> dfs.permissions=false should be an optional, non-default configuration that some sites
may decide to use.  It is further defined in HADOOP-2543.

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