GitHub user tgroh opened a pull request: https://github.com/apache/beam/pull/1941
Inject number of Shards as a Side Input to Write 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 permits users to pass a PTransform from the input elements to the number of shards instead of requiring a constant amount. This enables sharding to be determined based on the input data rather than a constant value. This can also convert the DirectRunner to inject a custom sharding strategy in its override, rather than relying on bundling behavior. 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/1941.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 #1941 ---- commit 3f60decfe12ffee2f1d22982b7d696dd86edb7b5 Author: Thomas Groh <tg...@google.com> Date: 2017-02-07T23:16:19Z Inject number of Shards as a Side Input to Write This permits users to pass a PTransform from the input elements to the number of shards instead of requiring a constant amount. This enables sharding to be determined based on the input data rather than a constant value. Tests still should be written. This can also convert the DirectRunner to inject a custom sharding strategy in its override, rather than relying on custom 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. ---