GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/2040
Inject Sharding Strategy in the Direct 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`. (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 removes the need to have WriteBundles be a very
implementation-dependent override based on both the behavior of the
Write transform and the behavior of the DirectRunner.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam write_inject_sharding
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2040.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 #2040
----
commit 556e7837fe9cb113a5a736e5b226a6b6eab7efb9
Author: Thomas Groh <tg...@google.com>
Date: 2017-02-18T00:52:27Z
Inject Sharding Strategy in the Direct Runner
This removes the need to have WriteBundles be a very
implementation-dependent override based on both the behavior of the
Write transform and the behavior of the DirectRunner.
----
---
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.
---
