hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5758) NameNode: complete implementation of inode modifications for ACLs.
Date Thu, 16 Jan 2014 23:03:22 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874113#comment-13874113

Haohui Mai commented on HDFS-5758:

bq. This sounds like a scenario where one person is responsible for chmod and another person
is responsible for setfacl, and you want to be able to tell who did which part of it. Is that

I'm referring to distinguishing the ACLs that are generated and the ones are specified by
setfacl / chmod.

bq. There are 4 distinct scenarios that can cause reduction of an extended ACL to a minimal

 I see it as an optimization. Can you keep it in a separate patch?
Based on your description, it seems to me that in {{removeAcl}}, the task can be done via
looking up the group entries and set the permission back. Note that the look up can be done
efficiently since the list is sorted. You might be able to get rid of the filter function.

> 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

View raw message