[ 
https://issues.apache.org/jira/browse/BEAM-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007755#comment-16007755
 ] 

ASF GitHub Bot commented on BEAM-2258:
--------------------------------------

GitHub user hepeknet opened a pull request:

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

    [BEAM-2258] BigtableIO should use AutoValue for read and 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-2258] BigtableIO should use AutoValue for read and write`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] 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).
    
    @dhalperi please check this... thanks
    ---


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

    $ git pull https://github.com/hepeknet/beam BEAM-2258

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

    https://github.com/apache/beam/pull/3113.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 #3113
    
----
commit 8b20981ab5ca3ef2c0d2d58736d1d188af491152
Author: Borisa Zivkovic <[email protected]>
Date:   2017-05-12T07:44:20Z

    BigtableIO should use AutoValue for read and write

----


> BigtableIO should use AutoValue for read and write
> --------------------------------------------------
>
>                 Key: BEAM-2258
>                 URL: https://issues.apache.org/jira/browse/BEAM-2258
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>            Reporter: Borisa Zivkovic
>            Assignee: Borisa Zivkovic
>            Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to