You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/12/26 23:27:50 UTC

[jira] [Commented] (HDFS-5613) NameNode: implement handling of ACLs in combination with symlinks.

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

Chris Nauroth commented on HDFS-5613:
-------------------------------------

I expect that no actual code changes are required to support ACLs in combination with symlinks.  {{FSPermissionChecker}} already knows how to follow the symlink when necessary before doing the permission check, and the patch in HDFS-5612 will enforce permissions for ACLs, so I expect the two will work together.  I'm still going to leave this issue open so that we can add tests to {{TestPermissionSymlinks}} to cover it.

> NameNode: implement handling of ACLs in combination with symlinks.
> ------------------------------------------------------------------
>
>                 Key: HDFS-5613
>                 URL: https://issues.apache.org/jira/browse/HDFS-5613
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS ACLs (HDFS-4685)
>            Reporter: Chris Nauroth
>
> A symlink in HDFS does not have an ACL of its own.  Operations that modify the ACL of a symlink instead modify the target of the symlink.  For operations that enforce ACLs, enforcement is on the target of the symlink.  This is similar to existing handling of permissions for symlinks.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)