[
https://issues.apache.org/jira/browse/HDFS-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Lamb updated HDFS-6375:
-------------------------------
Attachment: HDFS-6375.11.patch
Andrew,
I know what you mean about how we should be using an array, but looking at all
the other protocols, the common denominator that is required by decode on the
client side is a Map<?, ?>.
In any case, .11 adds the casting "fix" that you came up with.
> Listing extended attributes with the search permission
> ------------------------------------------------------
>
> Key: HDFS-6375
> URL: https://issues.apache.org/jira/browse/HDFS-6375
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Charles Lamb
> Attachments: HDFS-6375.1.patch, HDFS-6375.10.patch,
> HDFS-6375.11.patch, HDFS-6375.2.patch, HDFS-6375.3.patch, HDFS-6375.4.patch,
> HDFS-6375.5.patch, HDFS-6375.6.patch, HDFS-6375.7.patch, HDFS-6375.8.patch,
> HDFS-6375.9.patch
>
>
> From the attr(5) manpage:
> {noformat}
> Users with search access to a file or directory may retrieve a list of
> attribute names defined for that file or directory.
> {noformat}
> This is like doing {{getfattr}} without the {{-d}} flag, which we currently
> don't support.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
