[
https://issues.apache.org/jira/browse/HDFS-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628009#comment-13628009
]
Doug Cutting commented on HDFS-4683:
------------------------------------
With HADOOP-8689, a client that calls Trash#moveToTrash() is no longer be able
to bypass the trash but clients can still instead call FileSystem#delete() to
bypass the trash entirely. In other words, I believe that your (B) option is
already implemented.
> Per directory trash settings / trash override
> ---------------------------------------------
>
> Key: HDFS-4683
> URL: https://issues.apache.org/jira/browse/HDFS-4683
> Project: Hadoop HDFS
> Issue Type: Improvement
> Environment: Hadoop2
> Reporter: John Vines
>
> With the migration of trash settings to server side, it becomes more
> complicated for applications built on top of HDFS to properly deal with their
> trash. Applications like HBase and Accumulo already have a fair amount of
> trash management, adding the HDFS Trash will simply put more stress on DFS.
> But fully disabling the trash is overkill, as there still may be use for it
> in other uses of hadoop.
> I would like to request either:
> A. per directory or user trash settings, so that applications which work in a
> specific directory or use a specific user can continue to ignore the trash.
> B. An updated DistributedFileSystem delete() call which allows you to force
> ignoring the trash. I'm not sure how feasible this is due to the FileSystem
> API, but it may be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
