[
https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318065#comment-15318065
]
Tsz Wo Nicholas Sze commented on HADOOP-12910:
----------------------------------------------
> One of the key things that Deferred and Finagle's Future both enable is
> composition. This allows you to chain multiple asynchronous operations in a
> type-safe fashion. ...
Thanks for the comments. The dilemma here is that we want to use
CompletableFuture in trunk but it is unavailable in branch-2. My suggestion
indeed is that we only provide minimum async support in branch-2 and have full
support in trunk. I originally thought that Future was good enough. However,
as you can see in the past comments, people want callbacks so that I proposed
FutureWithCallback. You are right that it won't support chaining.
> 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
> Attachments: HADOOP-12910-HDFS-9924.000.patch,
> HADOOP-12910-HDFS-9924.001.patch, HADOOP-12910-HDFS-9924.002.patch
>
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
