[
https://issues.apache.org/jira/browse/HADOOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601544#action_12601544
]
dhruba edited comment on HADOOP-3177 at 6/2/08 12:48 AM:
-------------------------------------------------------------------
This issue blocks h-1700 because DFSOutputStream.fsync() is not a public API
yet. More work is needed to make it accessible from an application.
One option would be to introduce FSDataOutputStream.fsync() API. It would
invoke reflection to see if the wrapperStream as has a method named "fsync". If
so, then it will invoke wrapperStream.fsync(), otherwise it will invoke
wrapperStream.flush(). Does this sound reasonable?
was (Author: dhruba):
This issue blocks h-1700 because DFSOutputStream.fsync() is not a public
API yet. More work is needed to make it accessible from an application.
One option would be to introduce FSDataOutputStream.fsync() API. It would
invoke reflection to see if the wrapperStream as han a methid named "fsync". If
so, then it will invoke wrapperStream.fsync(), otherwise it will invoke
wrapperStream.flush(). Does this sound reasonable?
> 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.
