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

Posted to hdfs-dev@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2014/01/08 23:48:51 UTC

[jira] [Resolved] (HDFS-5739) ACL RPC must allow null name or unspecified permissions in ACL entries.

     [ https://issues.apache.org/jira/browse/HDFS-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth resolved HDFS-5739.
---------------------------------

       Resolution: Fixed
    Fix Version/s: HDFS ACLs (HDFS-4685)
     Hadoop Flags: Reviewed

I committed the v2 patch to the HDFS-4685 feature branch.  Thanks again for the review, Haohui.

> ACL RPC must allow null name or unspecified permissions in ACL entries.
> -----------------------------------------------------------------------
>
>                 Key: HDFS-5739
>                 URL: https://issues.apache.org/jira/browse/HDFS-5739
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, namenode
>    Affects Versions: HDFS ACLs (HDFS-4685)
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: HDFS ACLs (HDFS-4685)
>
>         Attachments: HDFS-5739.1.patch, HDFS-5739.2.patch
>
>
> Currently, the ACL RPC defines ACL entries with required fields for name and permissions.  These fields actually need to be optional.  The name can be null to represent unnamed ACL entries, such as the file owner or mask.  Permissions can be null when passed in an ACL spec to remove ACL entries via {{FileSystem#removeAclEntries}}.



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