GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/182
Remove the DirectPipeline class
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).
---
Users who wish to use the DirectPipelineRunner should do so by creating
a new Pipeline with the runner set in the PipelineOptions.
Replace existing uses with TestPipeline, and DataflowAssert if necessary.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam remove_direct_pipeline
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/182.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 #182
----
commit 18cb824ca3a4e2e537289f76fb52b6829d7d52f0
Author: Thomas Groh <tg...@google.com>
Date: 2016-04-14T23:12:23Z
Remove the DirectPipeline class
Users who wish to use the DirectPipelineRunner should do so by creating
a new Pipeline with the runner set in the PipelineOptions.
----
---
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.
---
