[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15333305#comment-15333305
]
Tsz Wo Nicholas Sze commented on HDFS-9924:
-------------------------------------------
> ... There is a callback API proposal for branch-2+trunk (Deferred) which
> would make everyone happy. ...
I think this statement is not yet confirmed. It seems that some people prefer
CompletableFuture in trunk. We need to verify it.
> So, let's just put it on a branch, and merge it for a later 2.x/3.x release.
> ...
The argument is about the API. So the branch is needed for HADOOP-12910, not
here.
> Per the bylaws, code integration is done based on consensus. ...
The bylaws clearly stated that "The code can be committed after the first +1".
We did follow it closely for the past JIRAs.
> [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: [email protected]
For additional commands, e-mail: [email protected]
