[ https://issues.apache.org/jira/browse/BEAM-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124313#comment-17124313 ]
Bharath Kumarasubramanian commented on BEAM-6550: ------------------------------------------------- Thanks for following up. I have a change in progress that covers API, Direct & Samza runner implementations. I ran into bunch of direct runner test failures. Will reopen the PR once I fix the tests. > 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 > Assignee: Bharath Kumarasubramanian > Priority: P2 > Labels: stale-assigned > 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)