Mahadev konar updated HADOOP-771:
---------------------------------
Attachment: Hadoop-771_3.patch
this patch fixes dhruba's comments.
Namenode should return error when trying to delete non-empty directory
----------------------------------------------------------------------
Key: HADOOP-771
URL: https://issues.apache.org/jira/browse/HADOOP-771
Project: Hadoop Core
Issue Type: Improvement
Components: dfs
Affects Versions: 0.8.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Mahadev konar
Attachments: Hadoop-771_2.patch, Hadoop-771_3.patch, patch_771_1.patch
Currently, the namenode.delete() method allows recursive deletion of a directory. That is, even a non-empty directory could be deleted using namenode.delete(). To avoid costly programmer errors, the namenode should not remove the non-empty directories in this method. Recursively deleting directory should either be performed with listPaths() followed by a delete() for every path, or with a specific namenode method such as deleteRecursive().
------------------------------------------------------------------------
Key: HADOOP-771
URL: https://issues.apache.org/jira/browse/HADOOP-771
Project: Hadoop Core
Issue Type: Improvement
Components: dfs
Affects Versions: 0.8.0
Environment: all
Reporter: Milind Bhandarkar
Assignee: Mahadev konar
Attachments: Hadoop-771_2.patch, Hadoop-771_3.patch, patch_771_1.patch
Currently, the namenode.delete() method allows recursive deletion of a directory. That is, even a non-empty directory could be deleted using namenode.delete(). To avoid costly programmer errors, the namenode should not remove the non-empty directories in this method. Recursively deleting directory should either be performed with listPaths() followed by a delete() for every path, or with a specific namenode method such as deleteRecursive().
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
