[
https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303008#comment-15303008
]
Tsz Wo Nicholas Sze commented on HADOOP-12910:
----------------------------------------------
> Can we introduce our own ListenableFuture class? Or use callbacks instead of
> Future? Listener or callback is very useful for writing event-driven programs.
It seems like a good idea to have our own Future sub-interface.
> Use Deferred, ...
I guess it may not be a good idea since it introduces an external dependency at
API level.
> Target this for 3.0 and use CompletableFuture. ...
Why making the entire async feature unavailable in branch 2? CompletableFuture
is nice-to-have but not must-have.
I suggest returning Future (or a sub-interface to support callbacks) in branch
2 and CompletableFuture (or our own implementation of CompletableFuture) in
trunk. In this way, trunk is backward compatible to branch 2 since
CompletableFuture implements Future.
> 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]
