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

stack commented on HDFS-9924:
-----------------------------

Your summary and characterization of where the discussion is at is not correct 
[~arpit99]. The discussion is ongoing still (CompletableFuture is a significant 
undertaking, ListenableFuture copied local or something like is a possible 
candidate, etc.)

bq. Since some downstream developers have expressed an interest in trying out a 
2.x Future-based API even if it's tagged as Unstable/Experimental, is there a 
compelling reason to deny it?

I'd hope that it takes more than 'interest' to get code committed to HDFS.

bq. If Future turns to be of no use to anyone we can evolve the API in a later 
2.x release or just revert it completely while the way forward (3.x) remains 
unaffected.

If a technical argument on why Future will fix a codebases's scaling problem 
can't be produced, we can just skip the above evolutions and reverts altogether.


> [umbrella] Asynchronous HDFS Access
> -----------------------------------
>
>                 Key: HDFS-9924
>                 URL: https://issues.apache.org/jira/browse/HDFS-9924
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: fs
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Xiaobing Zhou
>         Attachments: AsyncHdfs20160510.pdf
>
>
> This is an umbrella JIRA for supporting Asynchronous HDFS Access.
> Currently, all the API methods are blocking calls -- the caller is blocked 
> until the method returns.  It is very slow if a client makes a large number 
> of independent calls in a single thread since each call has to wait until the 
> previous call is finished.  It is inefficient if a client needs to create a 
> large number of threads to invoke the calls.
> We propose adding a new API to support asynchronous calls, i.e. the caller is 
> not blocked.  The methods in the new API immediately return a Java Future 
> object.  The return value can be obtained by the usual Future.get() method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to