[
https://issues.apache.org/jira/browse/HADOOP-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557113#action_12557113
]
Hadoop QA commented on HADOOP-2552:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12372743/HADOOP-2552.patch
against trunk revision .
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1518/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1518/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1518/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1518/console
This message is automatically generated.
> 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
> Assignee: Doug Cutting
> Fix For: 0.16.0
>
> Attachments: HADOOP-2552.patch
>
>
> 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.
