Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 20058 invoked from network); 19 Jul 2008 01:27:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jul 2008 01:27:01 -0000 Received: (qmail 28918 invoked by uid 500); 19 Jul 2008 01:27:00 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 28884 invoked by uid 500); 19 Jul 2008 01:27:00 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 28870 invoked by uid 99); 19 Jul 2008 01:27:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jul 2008 18:27:00 -0700 X-ASF-Spam-Status: No, hits=-1999.8 required=10.0 tests=ALL_TRUSTED,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jul 2008 01:26:07 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B3E1C234C1B6 for ; Fri, 18 Jul 2008 18:26:32 -0700 (PDT) Message-ID: <2061261887.1216430792735.JavaMail.jira@brutus> Date: Fri, 18 Jul 2008 18:26:32 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-1700) Append to files in HDFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1700?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1700: ------------------------------------- Status: Patch Available (was: Open) > Append to files in HDFS > ----------------------- > > Key: HADOOP-1700 > URL: https://issues.apache.org/jira/browse/HADOOP-1700 > Project: Hadoop Core > Issue Type: New Feature > Components: dfs > Affects Versions: 0.15.1 > Reporter: stack > Assignee: dhruba borthakur > Attachments: 1700_20080606.patch, append.patch, append3.patch, Ap= pends.doc, Appends.doc, Appends.html, appendtrunk10.patch, appendtrunk11.pa= tch, appendtrunk12.patch, appendtrunk13.patch, appendtrunk13.patch, appendt= runk13.patch, appendtrunk14.patch, appendtrunk14.patch, appendtrunk15.patch= , appendtrunk6.patch, appendtrunk7.patch, appendtrunk8.patch, appendtrunk9.= patch, Grid_HadoopRenumberBlocks.pdf > > > Request for being able to append to files in HDFS has been raised a coupl= e of times on the list of late. For one example, see http://www.nabble.co= m/HDFS%2C-appending-writes-status-tf3848237.html#a10916193. Other mail des= cribes folks' workarounds because this feature is lacking: e.g. http://www.= nabble.com/Loading-data-into-HDFS-tf4200003.html#a12039480 (Later on this t= hread, Jim Kellerman re-raises the HBase need of this feature). HADOOP-337= 'DFS files should be appendable' makes mention of file append but it was o= pened early in the life of HDFS when the focus was more on implementing the= basics rather than adding new features. Interest fizzled. Because HADOOP= -337 is also a bit of a grab-bag -- it includes truncation and being able t= o concurrently read/write -- rather than try and breathe new life into HADO= OP-337, instead, here is a new issue focused on file append. Ultimately, b= eing able to do as the google GFS paper describes -- having multiple concur= rent clients making 'Atomic Record Append' to a single file would be sweet = but at least for a first cut at this feature, IMO, a single client appendin= g to a single HDFS file letting the application manage the access would be = sufficent. --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.