[
https://issues.apache.org/jira/browse/HDFS-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004223#comment-14004223
]
Colin Patrick McCabe commented on HDFS-6375:
--------------------------------------------
bq. 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).
Yes, the parent directory is the correct semantic, similar to how unlink()
works. You don't need write permission on a file to unlink it... just on the
enclosing directory.
> 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, HDFS-6375.5.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)
