[HDFS-8831] Trash Support for deletion in HDFS encryption zone

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: encryption
• Hadoop Flags: Reviewed

Release Note

Add Trash support for deleting files within encryption zones. Deleted files will remain encrypted and they will be moved to a “.Trash” subdirectory under the root of the encryption zone, prefixed by $USER/current. Checkpoint and expunge continue to work like the existing Trash.

• Assignee: Xiaoyu Yao
• Reporter: Xiaoyu Yao
• Created: 28/Jul/15 20:08
• Updated: 03/Apr/17 23:09
• Resolved: 04/Dec/15 18:44

Description

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

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.

This JIRA is proposed to support trash for deletion of files within encryption zone.

Issue Links

• breaks: HDFS-9799 Reimplement getCurrentTrashDir to remove incompatibility
• breaks: HADOOP-13700 Remove unthrown IOException from TrashPolicy#initialize and #getInstance signatures
• contains: HDFS-8747 Provide Better "Scratch Space" and "Soft Delete" Support for HDFS Encryption Zones
• is broken by: HDFS-10324 Trash directory in an encryption zone should be pre-created with correct permissions
• is related to: HDFS-9844 Correct path creation in getTrashRoot to handle root dir
• is related to: HADOOP-13534 Remove unused TrashPolicy#getInstance and initialize code
• relates to: HADOOP-12661 Add trash APIs to the FileSystem specification
• relates to: HADOOP-7310 Trash location needs to be revisited