[
https://issues.apache.org/jira/browse/BEAM-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257441#comment-17257441
]
Beam JIRA Bot commented on BEAM-6550:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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, stale-P2
> 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)
