hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4918) HDFS permission check is incorrect
Date Wed, 19 Jun 2013 05:51:22 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687637#comment-13687637

Tsz Wo (Nicholas), SZE commented on HDFS-4918:

> so, If snapshot is null, all permission check are all did by "other class".

Why?  When snapshot is null, inode.getUserName(snapshot) returns the current owner of the
> 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

View raw message