[
https://issues.apache.org/jira/browse/HDFS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427649#comment-13427649
]
Todd Lipcon commented on HDFS-3755:
-----------------------------------
bq. Todd, I am not sure if this is the right behavior. Perhaps branch-1
behavior itself is incorrect. When another client is holding the lease, I do
not think we should allow create with overwrite=true to delete the file.
Why not? Doesn't "overwrite" imply that you wish to delete prior to creating a
new file? In the same way that we allow deleting an open file, I think we
should allow the atomic delete-and-recreate that overwrite implies.
> 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
