You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Rushabh S Shah (JIRA)" <ji...@apache.org> on 2018/01/18 20:06:00 UTC
[jira] [Created] (HDFS-13035) Owner should be able to set xattr if
not already set.
Rushabh S Shah created HDFS-13035:
-------------------------------------
Summary: Owner should be able 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
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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org