GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/651
[BEAM-434] Control the number of output shards 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).
---
Add a Write Override Factory that limits the number of shards is
unspecified. This ensures that we will not write an output file per-key
due to bundling.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam write_sharding
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/651.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 #651
----
commit dfecd170d67c90ae20a4baed3986bd1c7116e79e
Author: Thomas Groh <tg...@google.com>
Date: 2016-07-13T21:26:10Z
Control the number of output shards in the Direct Runner
Add a Write Override Factory that limits the number of shards is
unspecified. This ensures that we will not write an output file per-key
due to bundling.
----
---
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.
---
