GitHub user tgroh opened a pull request: https://github.com/apache/beam/pull/2315
Hide the isStreaming PipelineOption 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 is automatically inferred when necessary in all existing runners. Users should not need to set it unless they wish to force an alternative execution environment in a runner that respects this flag while running a Bounded Pipeline. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tgroh/beam hide_isStreaming Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2315.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 #2315 ---- commit 50f0c12fc6facaba7f31440193b5caad789fd009 Author: Thomas Groh <tg...@google.com> Date: 2017-03-24T17:28:23Z Hide the isStreaming PipelineOption This is automatically inferred when necessary in all existing runners. Users should not need to set it unless they wish to force an alternative execution environment in a runner that respects this flag while running a Bounded Pipeline. ---- --- 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. ---