[
https://issues.apache.org/jira/browse/HADOOP-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586566#action_12586566
]
Doug Cutting commented on HADOOP-771:
-------------------------------------
> Should we deprecate FileUtil.fullyDelete(FileSystem fs, Path dir)?
+1. Not only is it redundant, but it still uses the pre-URI style of passing
both a FileSystem and a Path, making it doubly-redundant too, in addition, as
well and so on.
> 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
> Fix For: 0.17.0
>
> Attachments: Hadoop-771_2.patch, Hadoop-771_3.patch,
> Hadoop-771_4.patch, Hadoop-771_5.patch, Hadoop-771_6.patch,
> Hadoop-771_7.patch, Hadoop-771_8.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.
