Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <601760640.1216160371704.JavaMail.jira@brutus>
Date: Tue, 15 Jul 2008 15:19:31 -0700 (PDT)
From: "Pete Wyckoff (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (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


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

Pete Wyckoff commented on HADOOP-3485:
--------------------------------------

Can one of you do a code review on the patch and we can then ask Doug or someone to commit this?

thx, pete


> 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
>            Assignee: Pete Wyckoff
>            Priority: Minor
>         Attachments: patch1.txt, patch2.txt, patch3.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.