hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls
Date Sun, 13 Mar 2016 14:02:33 GMT

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

Steve Loughran commented on HADOOP-12910:

In HADOOP-9965 I've been wondering if we could have a method "hasFeature(String):" -> yes,
no, don-know; we'd have standard strings to probe "append", "flush", .... The same probe could
do "serializable", "lineralizable", ...

To be fair, most code shouldn't be checking this stuff as there should be a common set of
assumptions: Filesystems look like HDFS, asyc operations have no guarantees on ordering. But
some things (distCp , output committers) may benefit if they probe for it, and the FS implementations
are honest in their replies

> Add new FileSystem API to support asynchronous method calls
> -----------------------------------------------------------
>                 Key: HADOOP-12910
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12910
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Xiaobing Zhou
> Add a new API, namely FutureFileSystem (or AsynchronousFileSystem, if it is a better
name).  All the APIs in FutureFileSystem are the same as FileSystem except that the return
type is wrapped by Future, e.g.
> {code}
>   //FileSystem
>   public boolean rename(Path src, Path dst) throws IOException;
>   //FutureFileSystem
>   public Future<Boolean> rename(Path src, Path dst) throws IOException;
> {code}
> Note that FutureFileSystem does not extend FileSystem.

This message was sent by Atlassian JIRA

View raw message