[ http://issues.apache.org/jira/browse/HADOOP-432?page=comments#action_12454242 ] dhruba borthakur commented on HADOOP-432: -----------------------------------------
I have two questions: 1. The trash directory is hardcoded to /trash. Does it make sense to introduce yet another config variable dfs.thrash.dir to allow the administrator to set the trash directory? 2. The code allows undeleting a file. The act of "undeleting" moves the file from /trash to its original location. Suppose I had a file named /user/dhruba/input/file.txt; I deleted it and it moved to /trash/user/dhruba/input/file.txt. Now I deleted the directory /user/dhruba/input. Then I tried to undelete the above file. Will the "/user/dhruba/input" directory get recreated in the process? ( An alternative would be to not have the "undelete" but an user can browse the /trash directory and copy files from /trash to anywhere else in his namespace). > support undelete, snapshots, or other mechanism to recover lost files > --------------------------------------------------------------------- > > Key: HADOOP-432 > URL: http://issues.apache.org/jira/browse/HADOOP-432 > Project: Hadoop > Issue Type: Improvement > Components: dfs > Reporter: Yoram Arnon > Assigned To: Wendy Chien > Attachments: undelete.patch, undelete11.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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
