[GitHub] beam pull request #2118: [BEAM-111] Move WritableCoder to hadoop-common

2017-03-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2118: [BEAM-111] Move WritableCoder to hadoop-common

2017-02-27 Thread iemejia
GitHub user iemejia opened a pull request:

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

[BEAM-111] Move WritableCoder to hadoop-common

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [x] Make sure the PR title is formatted like:
   `[BEAM-] Description of pull request`
 - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [x] 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.txt).

---


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

$ git pull https://github.com/iemejia/beam BEAM-111-move-writablecoder

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

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


commit 14dfc21567464fbc62a332b97f67bad928d50a18
Author: Ismaël Mejía 
Date:   2017-02-25T04:20:58Z

[BEAM-111] Move WritableCoder to hadoop-common




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