[
https://issues.apache.org/jira/browse/HDFS-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687661#comment-13687661
]
Prashant Kommireddi commented on HDFS-4918:
-------------------------------------------
We don't have very tight security requirements on our cluster at this point,
and it felt easier to disable the perms for now (that is how we also operated
0.20.2). In this case specifically, I don't think enabling perms would make a
difference as there would be an issue with another user (other than the one
that started the server) from writing to some directories?
I guess the question is more about backward-compatibility and also if the
feature (dfs.permissions.enabled) is actually expected to behave as its
documented. We can turn on perms if required, but the issue still remains.
> 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
