beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sb2nov <...@git.apache.org>
Subject [GitHub] beam pull request #2047: [BEAM-1218] Move GCP specific IO into separate modu...
Date Sun, 19 Feb 2017 18:58:58 GMT
GitHub user sb2nov opened a pull request:

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

    [BEAM-1218] Move GCP specific IO into separate module

    PR 1/? for moving the GCP IO stuff out. I'll refactor the IO channel factory next. 
    R: @aaltay PTAL
    
    
    
    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.txt).
    
    ---


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

    $ git pull https://github.com/sb2nov/beam BEAM-1218-Move-GCP-specific-IO

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

    https://github.com/apache/beam/pull/2047.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 #2047
    
----
commit d262a598331b26e233f6fd779b357a2dc710c6cd
Author: Sourabh Bajaj <sourabhbajaj@google.com>
Date:   2017-02-19T06:52:06Z

    [BEAM-1218] Move GCP specific IO into separate module

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message