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 "Pete Wyckoff (JIRA)" <ji...@apache.org> on 2008/06/28 00:43:44 UTC
[jira] Created: (HADOOP-3661) 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)
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
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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch2.txt
> 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, patch2.txt, patch2.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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616761#action_12616761 ]
Hadoop QA commented on HADOOP-3661:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386672/patch2.txt
against trunk revision 679601.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2945/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2945/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2945/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2945/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, patch2.txt, patch2.txt, patch2.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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624744#action_12624744 ]
Hudson commented on HADOOP-3661:
--------------------------------
Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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
> Fix For: 0.19.0
>
> Attachments: patch0.txt, patch0.txt, patch1.txt, patch2.txt, patch2.txt, patch2.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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Zheng Shao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614927#action_12614927 ]
Zheng Shao commented on HADOOP-3661:
------------------------------------
1.
<code>
if (dfs->nowrites || hdfsDelete(dfs->fs, path)) {
syslog(LOG_ERR,"ERROR: hdfs trying to delete the directory %s",path);
return -EIO;
</code>
Can we replace that with "ERROR: hdfs is configured as read-only, cannot delete the directory %s"
2. Is there any way NOT to hard code "/lib/amd64/server"?
Other things look good to me.
> 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
>
>
> 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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch0.txt
> 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
>
>
> 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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Open (was: Patch Available)
> 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, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Assignee: Robert Chansler (was: Pete Wyckoff)
Status: Open (was: Patch Available)
> 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: Robert Chansler
> Attachments: patch0.txt, patch0.txt, patch1.txt, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Patch Available (was: Open)
> 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, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Assignee: Pete Wyckoff (was: Robert Chansler)
Status: Open (was: Patch Available)
> 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, patch2.txt, patch2.txt, patch2.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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615839#action_12615839 ]
Hadoop QA commented on HADOOP-3661:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386581/patch2.txt
against trunk revision 678915.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2924/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2924/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2924/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2924/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, patch2.txt, patch2.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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616454#action_12616454 ]
Hadoop QA commented on HADOOP-3661:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386672/patch2.txt
against trunk revision 679286.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2935/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2935/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2935/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2935/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: Robert Chansler
> Attachments: patch0.txt, patch0.txt, patch1.txt, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Open (was: Patch Available)
> 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, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Patch Available (was: Open)
hudson failed on unrelated problems so I am re-submitting this.
> 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, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch2.txt
fixed issues with patch applying.
> 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, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Patch Available (was: Open)
> 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, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Open (was: Patch Available)
> 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, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch1.txt
attaching after the unit test stuff so hudson will pick this up as the patch.
> 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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-3661:
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.19.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks Pete!
> 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
> Fix For: 0.19.0
>
> Attachments: patch0.txt, patch0.txt, patch1.txt, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Patch Available (was: Open)
> 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, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch0.txt
> 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
> Attachments: patch0.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Status: Patch Available (was: Open)
re-submitting again to force hudson to retry.
> 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: Robert Chansler
> Attachments: patch0.txt, patch0.txt, patch1.txt, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch2.txt
re-attaching the same one since hudson had some problem and I want it to run the same patch again.
> 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, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: patch1.txt
New patch fixing issues found from Zheng's code review
> 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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Assignee: Pete Wyckoff
Status: Patch Available (was: Open)
> 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
>
>
> 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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: (was: patch1.txt)
> 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.
[jira] Commented: (HADOOP-3661) 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)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616260#action_12616260 ]
Hadoop QA commented on HADOOP-3661:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386672/patch2.txt
against trunk revision 678915.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2926/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2926/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2926/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2926/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, patch2.txt, patch2.txt, patch2.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.
[jira] Updated: (HADOOP-3661) 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)
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3661:
---------------------------------
Attachment: TEST-TestFuseDFS.txt
This is the output of the unit tests.
> 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.