[HDFS-15982] Deleted data using HTTP API should be saved to the trash

• Type: New Feature
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Component/s: hdfs, hdfs-client, httpfs, webhdfs
• Labels: pull-request-available
• Target Version/s: 3.3.9
• Hadoop Flags: Incompatible change

Release Note

Incompatible change:

Webhdfs and httpfs DELETE API's default behaviour is going to be similar to Delete shell command. If config "fs.trash.interval" is set to value greater than 0, DELETE API will by-default try to move given file to .Trash dir (similar to Delete shell command's behaviour).
However, DELETE API will also have skiptrash query param available that can skip trash even if config "fs.trash.interval" is set to value greater than 0 (similar to skipTrash argument of Delete shell command).
Default value of skiptrash query param will be false.

API change:
curl -i -X DELETE "http://host:port/webhdfs/v1/path?op=DELETE [&recursive=true|false][&skiptrash=true|false]"

• Assignee: Unassigned
• Reporter: Bhavik Patel
• Created: 16/Apr/21 06:18
• Updated: 29/Nov/22 15:51

Description

If we delete the data from the Web UI then it should be first moved to configured/default Trash directory and after the trash interval time, it should be removed. currently, data directly removed from the system[This behavior should be the same as CLI cmd]

This can be helpful when the user accidentally deletes data from the Web UI.

Similarly we should provide "Skip Trash" option in HTTP API as well which should be accessible through Web UI.

Issue Links

• is duplicated by: HDFS-15983 Deleted data on the Web UI must be saved to the trash
• is duplicated by: HDFS-15984 Deleted data on the Web UI must be saved to the trash
• links to: GitHub Pull Request #2925
• links to: GitHub Pull Request #2927
• links to: GitHub Pull Request #2976
• links to: GitHub Pull Request #2976