Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <283141525.1208820921664.JavaMail.jira@brutus>
Date: Mon, 21 Apr 2008 16:35:21 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3250) Extend FileSystem API to allow
 appending to files
In-Reply-To: <1986969743.1208203145188.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591116#action_12591116 ] 

dhruba borthakur commented on HADOOP-3250:
------------------------------------------

+1 on Doug's proposal.

If the path exists and is not being written to, then append() will return a OutputStream to the file. If the path does not exist, then append will generate a IOException.

The DFSClient will issue ClientProtocol.append() call to the namenode. If the file was being written to by another writer but it has exceeded the soft-lease period, then the namenode would *start* a distributed lease recovery. However, it will not make the client wait for the recovery to complete. The namenode will return an AlreadyBeingCreatedException as if the soft-limit has not yet expired. 

> Extend FileSystem API to allow appending to files
> -------------------------------------------------
>
>                 Key: HADOOP-3250
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3250
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: fs
>            Reporter: dhruba borthakur
>
> Provide an API to allow applications to append data to pre-existing files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.