You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2009/03/03 19:42:56 UTC
[jira] Updated: (HADOOP-4970) Use the full path when move files to
.Trash/Current
[ https://issues.apache.org/jira/browse/HADOOP-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-4970:
------------------------------------
Release Note: Changed trash facility to use absolute path of the deleted file. (was: Absolute path of the deleted file will be used while moving to trash to make undelete possible.)
Hadoop Flags: [Incompatible change, Reviewed] (was: [Reviewed, Incompatible change])
Edit release note for publication.
> Use the full path when move files to .Trash/Current
> ---------------------------------------------------
>
> Key: HADOOP-4970
> URL: https://issues.apache.org/jira/browse/HADOOP-4970
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Prasad Chakka
> Assignee: Prasad Chakka
> Fix For: 0.20.0
>
> Attachments: hadoop-4970.2.patch, hadoop-4970.patch
>
>
> When a directory or file is deleted using rm or rmr, the subtree is moved directly to .Trash/Current. If there are two deleted objects with the same name but with different original paths it is not feasible to undelete them without storing additional information regarding the original paths. Instead if the full path of the deleting object is used while moving (replicating the complete path in .Trash/Current) it will be easier to undelete objects to its original paths.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.