[
https://issues.apache.org/jira/browse/HADOOP-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469614
]
Yoram Arnon commented on HADOOP-432:
------------------------------------
expunge(), as implemented, purges the entire trash, which I find too coarse.
I'd like to be able to expunge a subset of the trash, both to be able to remove
the oldest first, and also since in might results in a large load on the
namenode.
It would be nice if the code, when deleting a file, checked if the source file
is already in the trash and would expunge it rather than trying to move it
inside the trash. That could serve as an alternative to expunge() altogether -
deleting from the trash means expunging. A lot like deleting a message from the
deleted folder in outlook.
> 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.
