[
https://issues.apache.org/jira/browse/HADOOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522564
]
Sameer Paranjpye commented on HADOOP-1708:
------------------------------------------
> Anyway, a pending create which is never completed ...
Why? Yes, it is a departure from the current semantics, but something that is
quite intentional. Calling delete should be the responsibility of user code not
the client library. This issue is one of the steps towards introducing append.
With appends in place, we want exactly the behavior that when a client dies we
don't delete a pending file, so that it or another client can resume where it
left off.
> Ideally however, renaming and deletion should also work on file being
> created.
So, rather than revert the change, I'd vote for implementing this behavior.
> make files visible in the namespace as soon as they are created
> ---------------------------------------------------------------
>
> Key: HADOOP-1708
> URL: https://issues.apache.org/jira/browse/HADOOP-1708
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.15.0
>
> Attachments: 1708-20070820a.patch, atomicCreation2.patch
>
>
> In the current DFS implementation, a file appears in the namespace only when
> the creator closes the file. Also, if the namenode or the client dies before
> closing the file, the file never appears in the namespace.
> This issue will make files appear in the namespace as soon as it is created.
> Also, it will continue to remain in the namespace even if the creator dies
> before closing the file.
> This is related to HADOOP-89. It is different from HADOOP-89 because it does
> not attempt to make data visible as soon as it is written.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
