[
https://issues.apache.org/jira/browse/HADOOP-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693514#action_12693514
]
Hadoop QA commented on HADOOP-5551:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12404070/HADOOP-5551-v4.patch
against trunk revision 759398.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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 failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/76/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/76/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/76/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/76/console
This message is automatically generated.
> Namenode permits directory destruction on overwrite
> ---------------------------------------------------
>
> Key: HADOOP-5551
> URL: https://issues.apache.org/jira/browse/HADOOP-5551
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.1
> Reporter: Brian Bockelman
> Assignee: Brian Bockelman
> Priority: Critical
> Fix For: 0.19.2, 0.20.0
>
> Attachments: HADOOP-5551-v2.patch, HADOOP-5551-v3.patch,
> HADOOP-5551-v4.patch
>
>
> The FSNamesystem's startFileInternal allows overwriting of directories. That
> is, if you have a directory named /foo/bar and you try to write a file named
> /foo/bar, the file is written and the directory disappears.
> This is most apparent for folks using libhdfs directly, as overwriting is
> always turned on. Therefore, if libhdfs applications do not check the
> existence of a directory first, then they will permit new files to destroy
> directories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
