[
https://issues.apache.org/jira/browse/HDFS-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-7384:
--------------------------------
Attachment: HDFS-7384-010.patch
It looks like patch v9 dropped the {{PBHelper}} changes by mistake, so the
{{FsPermission}} was null in the protobuf message. I'm attaching patch v10,
which is the same as patch v9 + re-adding the {{PBHelper}} changes from v8. I
also made one minor change to a comment in
{{AclStatus#getEffectivePermission}}, just to clarify that a minimal ACL would
end up calculating intersection of the group permissions with itself. Of
course, this is a no-op, so it's still correct.
+1 for patch v10 pending Jenkins.
> 'getfacl' command and 'getAclStatus' output should be in sync
> -------------------------------------------------------------
>
> Key: HDFS-7384
> URL: https://issues.apache.org/jira/browse/HDFS-7384
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HDFS-7384-001.patch, HDFS-7384-002.patch,
> HDFS-7384-003.patch, HDFS-7384-004.patch, HDFS-7384-005.patch,
> HDFS-7384-006.patch, HDFS-7384-007.patch, HDFS-7384-008.patch,
> HDFS-7384-009.patch, HDFS-7384-010.patch
>
>
> *getfacl* command will print all the entries including basic and extended
> entries, mask entries and effective permissions.
> But, *getAclStatus* FileSystem API will return only extended ACL entries set
> by the user. But this will not include the mask entry as well as effective
> permissions.
> To benefit the client using API, better to include 'mask' entry and effective
> permissions in the return list of entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
