[
https://issues.apache.org/jira/browse/HDFS-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337089#comment-16337089
]
Xiao Chen commented on HDFS-13035:
----------------------------------
[~andrew.wang] obviously has more weight to comment.
The proposed relaxation of a+b for file owner to set feinfo SGTM.
Question: what if the owner typo'ed and set a wrong xattr, then wanted to
remove? Do we relax it for {{removeXAttr}} and \{{getXAttrs}} as well (which
sounds fine too for xattr in general, but less so for fe info...)?
> Owner should be allowed to set xattr if not already set.
> --------------------------------------------------------
>
> Key: HDFS-13035
> URL: https://issues.apache.org/jira/browse/HDFS-13035
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs, namenode
> Reporter: Rushabh S Shah
> Priority: Major
>
> Motivation: This is needed to support encryption zones on WebhdfsFileSystem.
> For writing into EZ directory, webhdfs client will encrypt data on client
> side and will always write into /.reserved/raw/ directory so that datanode
> will not encrypt since its writing to /.reserved/raw directory.
> But then we have to somehow set crypto related x-attrs on the file.
> Currently only super user is allowed to set x-attrs.
> So I am proposing that the file owner(and superuser) should be allowed to set
> crypto related x-attrs if they are already not set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
