[GitHub] beam pull request #2470: [BEAM-1865]: Fix GroupByKeyInputVisitor for Direct ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/beam/pull/2470


---
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.
---

[GitHub] beam pull request #2470: [BEAM-1865]: Fix GroupByKeyInputVisitor for Direct ...

[vikkyrk]

GitHub user vikkyrk opened a pull request:

https://github.com/apache/beam/pull/2470

[BEAM-1865]: Fix GroupByKeyInputVisitor for 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-] 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 `` 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).

---

- Also handle `None` input types which is the case when 
`TypeOptions.pipeline_type_check` is disabled.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vikkyrk/incubator-beam py_gbk_type_check

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/beam/pull/2470.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 #2470


commit c7f1a44dc5259164f326bef23ff4620b4ffbcb77
Author: Vikas Kedigehalli 
Date:   2017-04-08T02:22:27Z

Fix GroupByKeyInputVisitor for Direct Runner




---
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.
---