[
https://issues.apache.org/jira/browse/HDFS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428252#comment-13428252
]
Hairong Kuang commented on HDFS-3755:
-------------------------------------
We do have a use case that a later running task may need to overwrite a file
being written because the old write may die. The way we do it is to delete the
file first and create a new one with the same path.
With the "overwritten" semantics that Todd introduced, we could cut one RPC
call to NameNode. This sounds a good semantics to have. We need to mark this
change incompatible, though.
> Creating an already-open-for-write file with overwrite=true fails
> -----------------------------------------------------------------
>
> Key: HDFS-3755
> URL: https://issues.apache.org/jira/browse/HDFS-3755
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3755.txt
>
>
> If a file is already open for write by one client, and another client calls
> {{fs.create()}} with {{overwrite=true}}, the file should be deleted and the
> new file successfully created. Instead, it is currently throwing
> AlreadyBeingCreatedException.
> This is a regression since branch-1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
