[
https://issues.apache.org/jira/browse/HADOOP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470732
]
Doug Cutting commented on HADOOP-432:
-------------------------------------
> a single invocation may result in a large load on the namenode
That's a namenode issue, not a trashcan issue. If deleting a large folder can
lock up the namenode for an unacceptable period, then the namenode should
address that, independent of whether the deletion happens via the trashcan, no?
So, unless there are more comments, I'll implement the feature where attempting
to move something that's already in the trash to the trash causes it to be
deleted, and re-submit this patch.
> support undelete, snapshots, or other mechanism to recover lost files
> ---------------------------------------------------------------------
>
> Key: HADOOP-432
> URL: https://issues.apache.org/jira/browse/HADOOP-432
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Reporter: Yoram Arnon
> Assigned To: Doug Cutting
> Attachments: trash.patch, undelete12.patch, undelete16.patch,
> undelete17.patch
>
>
> currently, once you delete a file it's gone forever.
> most file systems allow some form of recovery of deleted files.
> a simple solution would be an 'undelete' command.
> a more comprehensive solution would include snapshots, manual and automatic,
> with scheduling options.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
