GitHub user kennknowles opened a pull request: https://github.com/apache/beam/pull/1752
Make DataflowPipelineTranslator public There are a couple places outside the Beam codebase that still refer to this, and no great reason to break them. 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). --- R: @lukecwik You can merge this pull request into a Git repository by running: $ git pull https://github.com/kennknowles/beam DataflowPipelineTranslator-public Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1752.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 #1752 ---- commit 67dfe787c632450de688507da6efebfdf2bc9b44 Author: Kenneth Knowles <k...@google.com> Date: 2017-01-09T21:37:55Z Make DataflowPipelineTranslator public There are a couple places outside the Beam codebase that still refer to this, and no great reason to break them. ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---