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/02/13 00:00:20 UTC

[jira] [Resolved] (HDFS-5933) Optimize the FSImage layout for ACLs

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

Chris Nauroth resolved HDFS-5933.
---------------------------------

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

+1 for the v2 rebase patch.  I committed it to the HDFS-4685 branch.  Thanks again, Haohui.

> Optimize the FSImage layout for ACLs
> ------------------------------------
>
>                 Key: HDFS-5933
>                 URL: https://issues.apache.org/jira/browse/HDFS-5933
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client, namenode, security
>    Affects Versions: HDFS ACLs (HDFS-4685)
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>             Fix For: HDFS ACLs (HDFS-4685)
>
>         Attachments: HDFS-5933.000.patch, HDFS-5933.001.patch, HDFS-5933.002.patch
>
>
> The current serialization of the ACLs is suboptimal. ACL entries should be serialized using the same scheme that the PB-based FSImage serializes permissions.
>     
> An ACL entry is represented by a 32-bit integer in Big Endian format. The bits can be divided in four segments:
> [0:2) || [2:26) || [26:27) || [27:29) || [29:32)
> [0:2) -- reserved for futute uses.
> [2:26) -- the name of the entry, which is an ID that points to a string in the StringTableSection.
> [26:27) -- the scope of the entry (AclEntryScopeProto)
> [27:29) -- the type of the entry (AclEntryTypeProto)
> [29:32) -- the permission of the entry (FsActionProto)



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