beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Commented] (BEAM-831) ParDo Chaining
Date Mon, 01 May 2017 19:23:04 GMT


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

View raw message