You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/05/01 19:23:04 UTC

[jira] [Commented] (BEAM-831) ParDo Chaining

    [ https://issues.apache.org/jira/browse/BEAM-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991350#comment-15991350 ] 

Kenneth Knowles commented on BEAM-831:
--------------------------------------

This is not an API blocker, but I am adding it to First Stable Release to track it, hoping for the best.

> ParDo Chaining
> --------------
>
>                 Key: BEAM-831
>                 URL: https://issues.apache.org/jira/browse/BEAM-831
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Thomas Weise
>            Assignee: Chinmay Kolhatkar
>             Fix For: First stable release
>
>
> Current state of Apex runner creates a plan that will place each operator in a separate container (which would be processes when running on a YARN cluster). Often the ParDo operators can be collocated in same thread or container. Use Apex affinity/stream locality attributes for more efficient execution plan.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)