[
https://issues.apache.org/jira/browse/HDFS-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002550#comment-14002550
]
Charles Lamb commented on HDFS-6375:
------------------------------------
This is a clarification of the initial comment at the top of this Jira.
>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 statement is somewhat ambiguous in that it doesn't specify whether the
search access is to the file or directory on which the extended attributes
exist or the parent directory of the file/directory (on which the extended
attributes exist). It turns out that when one tries out extended attribute
commands on ext4, it's the latter. e.g. if you have /mydir/myfile and you have
extended attributes on myfile, then you need to have search access to myfile in
mydir.
> Listing extended attributes with the search permission
> ------------------------------------------------------
>
> Key: HDFS-6375
> URL: https://issues.apache.org/jira/browse/HDFS-6375
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: HDFS XAttrs (HDFS-2006)
> Reporter: Andrew Wang
> Assignee: Charles Lamb
> Attachments: HDFS-6375.1.patch, HDFS-6375.2.patch, HDFS-6375.3.patch,
> HDFS-6375.4.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)
