[
https://issues.apache.org/jira/browse/HDFS-8831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144891#comment-15144891
]
Zhe Zhang commented on HDFS-8831:
---------------------------------
[~xyao] [~arpitagarwal] [~leftnoteasy] [~andrew.wang] :
Since the new {{getCurrentTrashDir}} method is throwing an IOException, it
could break other applications using it. Should we mark this change as
incompatible? Alternatively, we should look at how to safely handle the
exception within HDFS.
> Trash Support for deletion in HDFS encryption zone
> --------------------------------------------------
>
> Key: HDFS-8831
> URL: https://issues.apache.org/jira/browse/HDFS-8831
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: encryption
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Fix For: 2.8.0
>
> Attachments: HDFS-8831-10152015.pdf, HDFS-8831.00.patch,
> HDFS-8831.01.patch, HDFS-8831.02.patch, HDFS-8831.03.patch,
> HDFS-8831.04.patch, HDFS-8831.05.patch
>
>
> Currently, "Soft Delete" is only supported if the whole encryption zone is
> deleted. If you delete files whinin the zone with trash feature enabled, you
> will get error similar to the following
> {code}
> rm: Failed to move to trash: hdfs://HW11217.local:9000/z1_1/startnn.sh:
> /z1_1/startnn.sh can't be moved from an encryption zone.
> {code}
> This JIRA is proposed to support trash for deletion of files within
> encryption zone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
