hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2657) Enhancements to DFSClient to support flushing data at any point in time
Date Fri, 07 Mar 2008 07:24:58 GMT

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

Raghu Angadi commented on HADOOP-2657:
--------------------------------------

I guess not. I was trying to figure out difference between in these two cases of reverting.

+1. 

> Enhancements to DFSClient to support flushing data at any point in time
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-2657
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2657
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: flush.patch, flush2.patch, flush3.patch, flush4.patch, flush5.patch
>
>
> The HDFS Append Design (HADOOP-1700) requires that there be a public API to flush data
written to a HDFS file that can be invoked by an application. This API (popularly referred
to a fflush(OutputStream)) will ensure that data written to the DFSOutputStream is flushed
to datanodes and any required metadata is persisted on Namenode.
> This API has to handle the case when the client decides to flush after writing data that
is not a exact multiple of io.bytes.per.checksum.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message