[
https://issues.apache.org/jira/browse/HADOOP-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth moved HDFS-5650 to HADOOP-10186:
----------------------------------------------
Component/s: (was: security)
(was: hdfs-client)
(was: namenode)
security
Fix Version/s: (was: HDFS ACLs (HDFS-4685))
HDFS ACLs (HDFS-4685)
Target Version/s: HDFS ACLs (HDFS-4685) (was: HDFS ACLs (HDFS-4685))
Affects Version/s: (was: HDFS ACLs (HDFS-4685))
HDFS ACLs (HDFS-4685)
Key: HADOOP-10186 (was: HDFS-5650)
Project: Hadoop Common (was: Hadoop HDFS)
> Remove AclReadFlag and AclWriteFlag in FileSystem API
> -----------------------------------------------------
>
> Key: HADOOP-10186
> URL: https://issues.apache.org/jira/browse/HADOOP-10186
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: HDFS ACLs (HDFS-4685)
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Fix For: HDFS ACLs (HDFS-4685)
>
> Attachments: HDFS-5650.000.patch, HDFS-5650.001.patch,
> HDFS-5650.002.patch, HDFS-5650.003.patch, HDFS-5650.004.patch,
> HDFS-5650.005.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.5#6160)