[jira] Commented: (HADOOP-2657) Enhancements to DFSClient to support flushing data at any point in time

["Raghu Angadi (JIRA)" <ji...@apache.org>]

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

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

Could you point me to specific portion of a documentation or description of what this is supposed to do? There are quite a few changes in DFSClient but none on DataNode? Not sure how that ensures data flushes that are not at the checksum chunk boundaries work.

Also, I think we should not require user not to flush before close. What is inefficient if user does flush() followed by close() instead of just close()?

> 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
>
>
> 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.