[
https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318041#comment-15318041
]
Tsz Wo Nicholas Sze commented on HADOOP-12910:
----------------------------------------------
> As to your FutureWithCallback, where does this come from? Have you built any
> event-driven apps with it? At first blush, it is lacking in vocabulary at
> least when put against Deferred or CompletableFuture. Thanks.
The idea of Callback and FutureWithCallback is similar to Java Event Model
which is a well-known model that many and many apps are built with it. I did
not intent to use it for replacing Deferred or CompletableFuture. As mentioned
previously, I propose using CompletableFuture for trunk. Unfortunately,
CompletableFuture is not available in branch-2 so that we need something like
FutureWithCallback to support callbacks.
> 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]
