hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8861) FSDataOutputStream.sync should call flush() if the underlying wrapped stream is not Syncable
Date Fri, 28 Sep 2012 05:57:07 GMT

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

Amareshwari Sriramadasu commented on HADOOP-8861:
-------------------------------------------------

I ran tests on branch-1, both commit and smoke tests pass. After that, the build fails saying
unable to delete userlog file. I see the same behavior in jenkins builds as well - https://builds.apache.org/job/Hadoop-1-Code-Coverage/159/consoleText
                
> 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
>         Attachments: 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

Mime
View raw message