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 "Brice Arnould (JIRA)" <ji...@apache.org> on 2008/04/15 14:29:05 UTC
[jira] Updated: (HADOOP-3127) rm /user//.Trash/____ only
moves it back to .Trash
[ https://issues.apache.org/jira/browse/HADOOP-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brice Arnould updated HADOOP-3127:
----------------------------------
Affects Version/s: (was: 0.16.1)
0.18.0
0.17.0
0.16.3
0.16.2
Status: Patch Available (was: Open)
Here is a patch and a test for this bug... It's my first patch to Hadoop, I just hope it is OK
> rm /user/<username>/.Trash/____ only moves it back to .Trash
> -------------------------------------------------------------
>
> Key: HADOOP-3127
> URL: https://issues.apache.org/jira/browse/HADOOP-3127
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.16.2, 0.16.3, 0.17.0, 0.18.0
> Reporter: Koji Noguchi
> Priority: Minor
>
> In 0.15 or before, any dfs -rm call for files under Trash were deleted.
> From 0.16, it just renames it back to Trash.
> In Trash.java:moveToTrash()
> {noformat}
> if (path.toString().startsWith(trash.toString()))
> {noformat}
> seems like trash.toString() is fully qualified, and path.toString() is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.