hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3177) Expose DFSOutputStream.fsync API though the FileSystem interface
Date Tue, 03 Jun 2008 21:32:45 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tsz Wo (Nicholas), SZE updated HADOOP-3177:

        Assignee: Tsz Wo (Nicholas), SZE  (was: dhruba borthakur)
    Release Note: Added a new public interface Syncable which declares the sync() operation.
 FSDataOutputStream implements Syncable.  If the wrappedStream in FSDataOutputStream is Syncalbe,
calling FSDataOutputStream.sync() is equivalent to call wrappedStream.sync().  Otherwise,
FSDataOutputStream.sync() is a no-op.  Both DistributedFileSystem and LocalFileSystem support
the sync() operation.
    Hadoop Flags: [Reviewed]
          Status: Patch Available  (was: Open)

> 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: Tsz Wo (Nicholas), SZE
>         Attachments: 3177_20080603.patch
> 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.

View raw message