hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13035) Owner should be allowed to set xattr if not already set.
Date Thu, 18 Jan 2018 20:57:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rushabh S Shah updated HDFS-13035:
----------------------------------
    Summary: Owner should be allowed to set xattr if not already set.  (was: Owner should
be able to set xattr if not already set.)

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message