[
https://issues.apache.org/jira/browse/HDFS-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845080#comment-13845080
]
Vinay commented on HDFS-5650:
-----------------------------
Hi Haohui,
I can see, its good not handle recursive requests at server side which may
create bad impact on performance. So we need to handle this from the client
side itself if required...?
Patch looks good,
One small nit in TestHarFileSystem, still using listAclStatus
{code}+ public AclStatus listAclStatus(Path path) throws IOException;{code}
> Remove AclReadFlag and AclWriteFlag in FileSystem API
> -----------------------------------------------------
>
> Key: HDFS-5650
> URL: https://issues.apache.org/jira/browse/HDFS-5650
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client, namenode, security
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-5650.000.patch, HDFS-5650.001.patch,
> HDFS-5650.002.patch, HDFS-5650.003.patch, HDFS-5650.004.patch
>
>
> AclReadFlag and AclWriteFlag intended to capture various options used in
> getfacl and setfacl. These options determine whether the tool should traverse
> the filesystem recursively, follow the symlink, etc., but they are not part
> of the core ACLs abstractions.
> The client program has more information and more flexibility to implement
> these options. This jira proposes to remove these flags to simplify the APIs.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
