[
https://issues.apache.org/jira/browse/HADOOP-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709612#action_12709612
]
stack commented on HADOOP-5744:
-------------------------------
A few comments and questions:
Document is without context. It is undated and has no author. In particular,
I'd think there'd be some positioning of this document in relation to previous
append work (Is hadoop-4379, etc., dead? Are we starting over as the name of
this issue portends. If starting over, is 0.21 fix version optimistic?).
What kind of 'delay' are we talking about here do you think in the section
Read, item #4 ? "If a writer/appender does not call hflush, a reader can still
progressively see previously written data with a delay"
> Revisit append
> --------------
>
> Key: HADOOP-5744
> URL: https://issues.apache.org/jira/browse/HADOOP-5744
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.21.0
>
> Attachments: AppendSpec.pdf
>
>
> HADOOP-1700 and related issues have put a lot of efforts to provide the first
> implementation of append. However, append is such a complex feature. It turns
> out that there are issues that were initially seemed trivial but needs a
> careful design. This jira revisits append, aiming for a design and
> implementation supporting a semantics that are acceptable to its users.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
