You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 07:14:00 UTC

[jira] [Updated] (HDFS-13035) Owner should be allowed to set xattr if not already set.

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

Shilun Fan updated HDFS-13035:
------------------------------
    Target Version/s: 3.5.0  (was: 3.4.0)

> 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 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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org