[
https://issues.apache.org/jira/browse/HDFS-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874037#comment-13874037
]
Haohui Mai commented on HDFS-5758:
----------------------------------
bq. Is there a benefit to that change (other than mimicking libacl)? I suppose
we could change getAclStatus like that, but it does mean that all potential
clients (not just getfacl) must do both a getFileStatus and a getAclStatus to
get a complete picture of permissions.
# It's difficult for the client to differentiate the ACLs you've generated and
the ones that the admins have specified. The client can easily calculate the
logical ACL by itself if the permissions and extended ACLs are separated.
# We have to implement optimizations to get rid of minimal ACLs.
It seems to me that in my proposal {{removeAclEntries}} cannot simply drops the
ACL features in the inode. Am I missing something?
> NameNode: complete implementation of inode modifications for ACLs.
> ------------------------------------------------------------------
>
> Key: HDFS-5758
> URL: https://issues.apache.org/jira/browse/HDFS-5758
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: HDFS ACLs (HDFS-4685)
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-5758.1.patch, HDFS-5758.2.patch
>
>
> This patch will complete the remaining logic for the ACL get and set APIs,
> including remaining work in {{FSNamesystem}}, {{FSDirectory}} and storage in
> the inodes.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
