[
https://issues.apache.org/jira/browse/HADOOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521630
]
Sameer Paranjpye commented on HADOOP-1708:
------------------------------------------
-1
The presence of abandonFileInProgress was a necessary side effect of files not
being visible when they were created. Now that they are, this is no longer
needed. In any case, the only reliable way to prevent clients from stepping on
each others toes is to use temporary filenames and then promote them to final
names as is done in map/reduce. A client that needs to call
abandonFileInProgress as your test case does can just as easily call delete.
> 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.
