[
https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614946#action_12614946
]
Hadoop QA commented on HADOOP-3661:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386452/patch1.txt
against trunk revision 678080.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2910/console
This message is automatically generated.
> Normalize fuse-dfs handling of moving things to trash wrt the way hadoop dfs
> does it (only when non posix trash flag is enabled in compile)
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3661
> URL: https://issues.apache.org/jira/browse/HADOOP-3661
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
> Assignee: Pete Wyckoff
> Attachments: patch0.txt, patch0.txt, patch1.txt, TEST-TestFuseDFS.txt
>
>
> Currently fuse-dfs is very crude about moving things to Trash. It can only
> move them once since it doesn't use any numbering scheme to prevent
> overwrites.
> Should look at the code that hadoop dfs uses to move things to the trash and
> have the same behavior, i think.
> Leaving it as major because it's pretty annoying and you can't tell what's
> wrong when you get an EIO when deleting something.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
