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

Viraj Jasani updated HDFS-15982:
--------------------------------
    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]"

  was:
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]"


> Deleted data using HTTP API should be saved to the trash
> --------------------------------------------------------
>
>                 Key: HDFS-15982
>                 URL: https://issues.apache.org/jira/browse/HDFS-15982
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: hdfs, hdfs-client, httpfs, webhdfs
>            Reporter: Bhavik Patel
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: Screenshot 2021-04-23 at 4.19.42 PM.png, Screenshot 
> 2021-04-23 at 4.36.57 PM.png
>
>          Time Spent: 8.5h
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to