hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6375) Listing extended attributes with the search permission
Date Fri, 16 May 2014 23:36:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000497#comment-14000497
] 

Chris Nauroth commented on HDFS-6375:
-------------------------------------

I agree that handling this as a separate API would be less error-prone, and it seems it would
be more consistent with existing implementations too.

bq. If you only have scan access then the method would not even return the name.

I didn't quite follow this statement, because I thought the point of scan access was to allow
the user to see the full list of xattr names even if that user isn't authorized to read the
values.  Could you please clarify?

> 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)

Mime
View raw message