[
https://issues.apache.org/jira/browse/HADOOP-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688383#action_12688383
]
Konstantin Shvachko commented on HADOOP-5551:
---------------------------------------------
Looks like your solution will work only if permission is enabled. If not it
will still replace the directory by the file.
Could you please include a test for that. You can just add a test case to
TestFileCreation in order to avoid cluster startup / shutdown just for this one
operation.
> Namenode permits directory destruction on overwrite
> ---------------------------------------------------
>
> Key: HADOOP-5551
> URL: https://issues.apache.org/jira/browse/HADOOP-5551
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.19.1
> Reporter: Brian Bockelman
> Priority: Critical
> Attachments: HADOOP-5551.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.
