GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/2615
Use the Input Coder in Dataflow Pubsub 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.pdf).
---
If no element coder is specified, and one is required, use the element
coder of the input PCollection as the encoding input. The coder is known
to have the appropriate type.
R: @reuvenlax
This is likely going away as part of
https://issues.apache.org/jira/browse/BEAM-1353;
we should require a `T -> bytes` conversion to be explicitly specified
rather than using a Coder.
Right now the input coder is not always defined. This fixes that bug.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam pubsub_write_coder
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2615.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 #2615
----
commit 4dd597621a9fce3fc95d6a265d4c9eaf70648326
Author: Thomas Groh <[email protected]>
Date: 2017-04-20T19:29:24Z
Use the Input Coder in Dataflow Pubsub Write
If no element coder is specified, and one is required, use the element
coder of the input PCollection as the encoding input. The coder is known
to have the appropriate type.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
