[
https://issues.apache.org/jira/browse/HDFS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317321#comment-14317321
]
Yongjun Zhang commented on HDFS-4685:
-------------------------------------
HI Chirs,
Thanks a lot for your quick answer. So if I understand it correctly, the
description in UC3 is conceptual. Implementation-wise, the owning group entry
is from the permission bits (where the owning group's permission is specified),
and the named group entry is from ACL data (where the other groups are
specified). When we do "hdfs -getfacl", it will print out them together as the
ACL for the target file. Right? Thanks.
> Implementation of ACLs in HDFS
> ------------------------------
>
> Key: HDFS-4685
> URL: https://issues.apache.org/jira/browse/HDFS-4685
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs-client, namenode, security
> Affects Versions: 1.1.2
> Reporter: Sachin Jose
> Assignee: Chris Nauroth
> Fix For: 2.4.0
>
> Attachments: HDFS-4685-branch-2.1.patch, HDFS-4685.1.patch,
> HDFS-4685.2.patch, HDFS-4685.3.patch, HDFS-4685.4.patch,
> HDFS-ACLs-Design-1.pdf, HDFS-ACLs-Design-2.pdf, HDFS-ACLs-Design-3.pdf,
> Test-Plan-for-Extended-Acls-1.pdf, Test-Plan-for-Extended-Acls-2.pdf
>
>
> Currenly hdfs doesn't support Extended file ACL. In unix extended ACL can be
> achieved using getfacl and setfacl utilities. Is there anybody working on
> this feature ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
