[
https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323775#comment-15323775
]
Tsz Wo Nicholas Sze commented on HADOOP-12910:
----------------------------------------------
Chaining/callbacks are nonessential in the sense that they can possibly be
provided by other library but async is not. Correct me if I am wrong.
I want to support chaining/callbacks but may not be necessarily in the first
step. We could first have async and then chaining+callbacks; or first
async+callbacks and then chaining. I wish supporting chaining is easy so that
I will just give you a patch. On the other hand, I do need the async feature.
I really like to know what's wrong about the AWT-style APIs registering
listener? You are right that AWT and the Observer pattern are probably from
90s or even earlier but ListenableFuture using the same approach was developed
recently.
The "rocket launching" was a bad joke. Sorry.
> 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]
