beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-831) ParDo Chaining
Date Mon, 08 May 2017 04:59:04 GMT

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

ASF GitHub Bot commented on BEAM-831:
-------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/2927


> 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: 2.0.0
>
>
> 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)

Mime
View raw message