[
https://issues.apache.org/jira/browse/HADOOP-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Bockelman updated HADOOP-5551:
------------------------------------
Status: Open (was: Patch Available)
> 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
>
>
> 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.
