[
https://issues.apache.org/jira/browse/HDFS-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687648#comment-13687648
]
Tsz Wo (Nicholas), SZE commented on HDFS-4918:
----------------------------------------------
> The issue (I don't think its snapshot related either) is that the NN RPC call
> of setPermission does not check the state of isPermissionsEnabled. ...
If permission is disabled, user should not call setPermission/setOwner since
setting them does not have the desired effect. Perhaps we should throw some
other exceptions such as IllegalStateException.
> HDFS permission check is incorrect
> ----------------------------------
>
> Key: HDFS-4918
> URL: https://issues.apache.org/jira/browse/HDFS-4918
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, namenode
> Affects Versions: 2.0.0-alpha
> Reporter: Fengdong Yu
>
> HDFS permisson check is incorrect, even if dfs.permissions is set false. it
> does look like this was caused by snap shot.
--
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
