[ 
https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317891#comment-15317891
 ] 

Jitendra Nath Pandey commented on HADOOP-12910:
-----------------------------------------------

+1 to use CompletableFuture in trunk. I see that a 
CompletableFutureWithCallback needs to be defined only so that we can have a 
FutureWithCallback in branch-2. We will need to evaluate how complicated that 
gets, but if its too hard, I would suggest, not to backport the user-facing API 
in branch-2 at all.
  Since CompletableFuture implements Future, there is still no incompatibility 
with the current code in branch-2. It is valid that branch-2 will not have all 
the cool features of CompletableFuture, but some early experimenters may be 
willing to live with that limitation, and will not run into incompatibility 
once upgrade to trunk. 

> 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]

Reply via email to