[ https://issues.apache.org/jira/browse/BEAM-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864094#comment-15864094 ]
ASF GitHub Bot commented on BEAM-646: ------------------------------------- GitHub user tgroh opened a pull request: https://github.com/apache/beam/pull/1995 [BEAM-646] Add ReplaceOutputs to PTransformOverrideFactory 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`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] 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.txt). --- This maps the outputs produced by applying a Replacement PTransform to the outputs produced by the original PTransform. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tgroh/beam replacement_output Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1995.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 #1995 ---- commit f46459d3179c7d3aaa675bff2f88e15fca1ae883 Author: Thomas Groh <tg...@google.com> Date: 2017-02-09T19:11:23Z Add ReplaceOutputs to PTransformOverrideFactory This maps the outputs produced by applying a Replacement PTransform to the outputs produced by the original PTransform. ---- > Get runners out of the apply() > ------------------------------ > > Key: BEAM-646 > URL: https://issues.apache.org/jira/browse/BEAM-646 > Project: Beam > Issue Type: Improvement > Components: beam-model-runner-api, sdk-java-core > Reporter: Kenneth Knowles > Assignee: Thomas Groh > > Right now, the runner intercepts calls to apply() and replaces transforms as > we go. This means that there is no "original" user graph. For portability and > misc architectural benefits, we would like to build the original graph first, > and have the runner override later. > Some runners already work in this manner, but we could integrate it more > smoothly, with more validation, via some handy APIs on e.g. the Pipeline > object. -- This message was sent by Atlassian JIRA (v6.3.15#6346)