[
https://issues.apache.org/jira/browse/HDFS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317272#comment-14317272
]
Yongjun Zhang commented on HDFS-4685:
-------------------------------------
Hi [~cnauroth],
Thanks for your earlier work on ACL. I have a question here.
When I read the design spec UC3 (Hive Partitioned Tables), it's said "This use
case can be implemented by setting an access ACL on each sub-directory
containing an owning group entry and a named group entry". Where the owning
group entry is equivalent to setting permission bits. My question is, if we
already have the permission bits that describes the owning group's permission,
why we need this owning group entry in the ACL?
Thanks for your time to answer the question.
> 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)
