GitHub user aviemzur reopened a pull request:

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

    [BEAM-1466] JSON utils extension

    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-<Jira issue #>] 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 `<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).
    
    ---


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

    $ git pull https://github.com/aviemzur/beam json-utils

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

    https://github.com/apache/beam/pull/1983.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 #1983
    
----
commit c222abcddf07509b5e6d3a4003d9da086f809d94
Author: Aviem Zur <[email protected]>
Date:   2017-02-11T15:06:45Z

    [BEAM-1466] JSON utils extension

commit bd82f2cd543559ceef73b6818828e2d54f77a370
Author: Aviem Zur <[email protected]>
Date:   2017-02-12T20:17:04Z

    Javadoc improvements.

commit 3c5e0da7a6e570c58a105f37e3ddd374cb4cb60c
Author: Aviem Zur <[email protected]>
Date:   2017-02-13T05:12:58Z

    Added test for writing with custom mapper.

commit d4d7173a592da6e91cd27b9c60951fb17c76c174
Author: Aviem Zur <[email protected]>
Date:   2017-02-20T19:47:08Z

    Changes after review.

----


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

Reply via email to