[
https://issues.apache.org/jira/browse/BEAM-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998991#comment-15998991
]
ASF GitHub Bot commented on BEAM-831:
-------------------------------------
GitHub user tweise opened a pull request:
https://github.com/apache/beam/pull/2927
[BEAM-831] ParDo Chaining of Apex Runner
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`.
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
---
R: @kennknowles
based on #2216
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/beam BEAM-831-ParDoChaining
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2927.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2927
----
commit e09aceff2276955edd481981013738a63d738bcb
Author: chinmaykolhatkar <[email protected]>
Date: 2017-03-01T11:29:46Z
[BEAM-831] ParDo Fusion of Apex Runner
commit cad694ae0f641b69e3a12eb15b82a3234b793216
Author: Thomas Weise <[email protected]>
Date: 2017-05-05T13:45:34Z
[BEAM-831] Adjustments to the chaining logic.
closes #2216
----
> 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)
