hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3177) Expose DFSOutputStream.fsync API though the FileSystem interface
Date Mon, 02 Jun 2008 18:15:45 GMT

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

Doug Cutting commented on HADOOP-3177:
--------------------------------------

> It would invoke reflection to see if the wrapperStream as has a method named "fsync".

Yuk.  What is the reason not to add a sync() method to FileSystem and/or FSDataOutputStream?

> Expose DFSOutputStream.fsync API though the FileSystem interface
> ----------------------------------------------------------------
>
>                 Key: HADOOP-3177
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3177
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> In the current code, there is a DFSOutputStream.fsync() API that allows a client to flush
all buffered data to the datanodes and also persist block locations on the namenode. This
API should be exposed through the generic API in the org.hadoop.fs.

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