[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322273#comment-15322273 ]
Tsz Wo Nicholas Sze commented on HADOOP-12910: ---------------------------------------------- After some thought, copying CompletionStage and CompletableFuture may not be straightforward since it requires to copy also the dependent classes such as the classes in the java.util.function package. So returning ListenableFuture seems like a better choice. > There is an additional tactical advantage with ListenableFuture. The current > implementation AsyncGetFuture already extends AbstractFuture that implements > ListenableFuture. So it seems pretty low hanging. ... That's correct. The current code already supports ListenableFuture although we keep the return type as 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: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org