[
https://issues.apache.org/jira/browse/HDFS-9924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321393#comment-15321393
]
Andrew Wang commented on HDFS-9924:
-----------------------------------
The API discussion is still unresolved, though it seems many people are
advocating for an API that is different from what is currently committed.
So, do we still see a benefit from having the current code committed to the
release branches vs. a feature branch? The code is also likely to change a lot
if the API changes. It's also only in DistributedFileSystem, so it's not used
by any current code paths. Finally, considering that we have multiple
downstream users saying they want a different API, it doesn't seem likely
they'll do much testing of the current DFS-level API anyway.
So for these reasons (though not well-communicated earlier), my preference is
to move this to a feature branch. Other contributors have also voiced similar
requests for a feature branch. As I said on the common-dev discussion, I'm
happy to review a future merge vote if there is a concern about getting three
+1's.
Somewhat separately, Vinod expressed a preference on common-dev for leaving new
features out of 2.8, since it's late in the release cycle.
Hoping we can reach consensus by end of week (Friday). I'm also happy to again
do the requisite git work.
> [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]
