Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 19 Oct 2012 19:58:16 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <200574568.2696.1350676696257.JavaMail.jiratomcat@arcas>
In-Reply-To: <690667296.133059.1348740367597.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HADOOP-8861) FSDataOutputStream.sync should
 call flush() if the underlying wrapped stream is not Syncable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Uma Maheswara Rao G commented on HADOOP-8861:
---------------------------------------------

I have just committed to branch-1. 
Committed revision 1400256.
                
> FSDataOutputStream.sync should call flush() if the underlying wrapped stream is not Syncable
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8861
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8861
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.0.3
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 1.2.0
>
>         Attachments: HADOOP-8861-2.patch, HADOOP-8861.patch
>
>
> Currently FSDataOutputStream.sync is a no-op if the wrapped stream is not Syncable. Instead it should call flush() if the wrapped stream is not syncable.
> This behavior is already present in trunk, but branch-1 does not have this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira