[
https://issues.apache.org/jira/browse/HADOOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522628
]
Konstantin Shvachko commented on HADOOP-1708:
---------------------------------------------
Yes we knew this changes the semantics of file creates, but we did not take
into account that semantics of deletes/renames will change too.
I do not think we have a consensus on what it should be.
Imho until we define the semantics and implement it the patch should be
reverted (if it is still possible).
> Ideally however, renaming and deletion should also work on file being created.
Would it be more consistent to forbid deletion of files that have active leases.
I agree rename should work on being created file, but then we will have to
introduce file ids for accessing files that have been opened.
> 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.
