Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 89469 invoked from network); 27 Jun 2008 22:40:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2008 22:40:36 -0000 Received: (qmail 89606 invoked by uid 500); 27 Jun 2008 22:40:36 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 89584 invoked by uid 500); 27 Jun 2008 22:40:36 -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 89572 invoked by uid 99); 27 Jun 2008 22:40:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2008 15:40:36 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED 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; Fri, 27 Jun 2008 22:39:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 01169234C14C for ; Fri, 27 Jun 2008 15:39:45 -0700 (PDT) Message-ID: <1209844049.1214606384989.JavaMail.jira@brutus> Date: Fri, 27 Jun 2008 15:39:44 -0700 (PDT) From: "Pete Wyckoff (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-3485) implement writes In-Reply-To: <898585815.1212517844973.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Wyckoff updated HADOOP-3485: --------------------------------- Attachment: patch1.txt I don't know what I was thinking before about writes not working. Must have been confused. There was a bug (the write not returning #bytes written) which I have fixed and also enabled create, write, mknod and flush. I'm including this now, but will wait to officially submit a patch until I have a unit test. > implement writes > ---------------- > > Key: HADOOP-3485 > URL: https://issues.apache.org/jira/browse/HADOOP-3485 > Project: Hadoop Core > Issue Type: New Feature > Components: contrib/fuse-dfs > Reporter: Pete Wyckoff > Priority: Minor > Attachments: patch1.txt > > Original Estimate: 48h > Remaining Estimate: 48h > > Doesn't support writes because fuse protocol first creates the file then closes it and re-opens it to start writing to it. So, (until hadoop-1700), we need a work around. > One way to do this is to open the file with overwrite flag on the second open. For security, would only want to do this for zero length files (could even check the creation ts too, but because of clock skew, that may be harder). > Doug, Craig, Nicholas - Comments? > -- pete > ps since mostly already implemented, this should be a very quick patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.