Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1768335692.1248287234938.JavaMail.jira@brutus>
Date: Wed, 22 Jul 2009 11:27:14 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-265) Revisit append
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734235#action_12734235 ] 

Hairong Kuang commented on HDFS-265:
------------------------------------

In this design, a new generation stamp is always fetched from NameNode before a new pipeline is set up when handling errors. So if an access token is also fetched along with the generation stamp, things should be OK.

> Revisit append
> --------------
>
>                 Key: HDFS-265
>                 URL: https://issues.apache.org/jira/browse/HDFS-265
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>         Attachments: appendDesign.pdf, appendDesign.pdf, appendDesign1.pdf, AppendSpec.pdf, TestPlanAppend.html
>
>
> 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.