[
https://issues.apache.org/jira/browse/HDFS-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351659#comment-17351659
]
Stephen O'Donnell commented on HDFS-16032:
------------------------------------------
I agree with [~ayushtkn]. It does not feel correct to enforce trash at the
existing delete API call. One other reason, is that there may be some reason a
call to delete does not want to use trash, so you need a "skipTrash" option,
which would break compatibility. Exposing a more public "deleteWithTrash" is
probably better, and then a user of the API can decide which they want to use.
> DFSClient#delete supports Trash
> --------------------------------
>
> Key: HDFS-16032
> URL: https://issues.apache.org/jira/browse/HDFS-16032
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hadoop-client, hdfs
> Affects Versions: 3.4.0
> Reporter: Xiangyi Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently, HDFS can only move deleted data to Trash through Shell commands.
> In actual scenarios, most of the data is deleted through DFSClient Api. I
> think it should support Trash.
--
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
