hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-12484) Undefined -expunge behavior after 2.8
Date Thu, 21 Sep 2017 08:48:01 GMT

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

Wei-Chiu Chuang updated HDFS-12484:
-----------------------------------
    Description: 
(Rewrote the description to reflect the actual behavior)
Hadoop 2.8 added a feature to support trash inside encryption zones, which is a great feature
to have.

However, when it comes to -expunge, the behavior is not well defined. A superuser invoking
-expunge removes files under all encryption zone trash directory belonging to the user. On
the other hand, because listEncryptionZones requires superuser permission, a non-privileged
user invoking -expunge can removes under home directory, but not under encryption zones.

Moreover, the command prints a scary warning message 

  was:
Hadoop 2.8 added a feature to support trash inside encryption zones, which is a great feature
to have.

However, it breaks the existing -expunge semantics because now a user must have superuser
permission in order to -expunge. The reason behind that is that -expunge gets all encryption
zone paths using DFSClient#listEncryptionZones, which requires super user permission.

Not sure what's the best way to address this, so file this jira to invite comments.


> Undefined -expunge behavior after 2.8
> -------------------------------------
>
>                 Key: HDFS-12484
>                 URL: https://issues.apache.org/jira/browse/HDFS-12484
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.8.0, 3.0.0-alpha1
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>         Attachments: HDFS-12484.001.patch, HDFS-12484.002.patch
>
>
> (Rewrote the description to reflect the actual behavior)
> Hadoop 2.8 added a feature to support trash inside encryption zones, which is a great
feature to have.
> However, when it comes to -expunge, the behavior is not well defined. A superuser invoking
-expunge removes files under all encryption zone trash directory belonging to the user. On
the other hand, because listEncryptionZones requires superuser permission, a non-privileged
user invoking -expunge can removes under home directory, but not under encryption zones.
> Moreover, the command prints a scary warning message 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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