[
https://issues.apache.org/jira/browse/HDFS-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494022#comment-17494022
]
Steve Loughran commented on HDFS-16032:
---------------------------------------
FYI this would
# destroy performance on s3a, where copy is used on rename
# make delete faster on abfs where oauth is used to authenticate, as there a
delete() call forces a treewalk of all directories to validate caller has the
permissions it needs. HADOOP-17691. But when ABFS starts throttling, renames()
may fail in ways that delete doesn't.
we are discussing adding a plugin point for per-schema trash: HADOOP-18013
it would be possible to add something in FileUtils to use this, but
FileSystem.delete() *must not* suddenly move things to trash.
> 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: 50m
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
