[
https://issues.apache.org/jira/browse/BEAM-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224897#comment-17224897
]
Andrew Pilloud commented on BEAM-6550:
--------------------------------------
Beam SQL has a use case for this. Right now I am [calling `.get` on a future in
processElement|https://github.com/apache/beam/pull/13238/files], I would get a
big performance boost if I didn't do that. Anything I can do to help move this
forward?
> ParDo Async Java API
> --------------------
>
> Key: BEAM-6550
> URL: https://issues.apache.org/jira/browse/BEAM-6550
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Xinyu Liu
> Priority: P2
> Labels: Clarified
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This ticket is to track the work on adding the ParDo async API. The
> motivation for this is:
> - Many users are experienced in asynchronous programming. With async
> frameworks such as Netty and ParSeq and libs like async jersey client, they
> are able to make remote calls efficiently and the libraries help manage the
> execution threads underneath. Async remote calls are very common in most of
> our streaming applications today.
> - Many jobs are running on a multi-tenancy cluster. Async processing helps
> for less resource usage and fast computation (less context switch).
> This API has become one of the most asked Java api from SamzaRunner users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
