GitHub user ssisk opened a pull request:

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

    [BEAM-2033] Add HadoopResourceId (attempt 2)

    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.
     - [X] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---
    Based on https://github.com/apache/beam/pull/2671 - now with more licenses! 
Also a serializable HadoopResourceId.
    
    We'd like this to go into a new feature branch. 
    
    R: @tgroh 

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

    $ git pull https://github.com/ssisk/beam hfs-pre-req

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

    https://github.com/apache/beam/pull/2681.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 #2681
    
----
commit 7379db04fbdbed3f8460d991b7789b08d8334745
Author: Stephen Sisk <[email protected]>
Date:   2017-04-22T00:23:55Z

    Add HadoopResourceId

commit 4dd919a35e09430973a1aabe0a77cc9df4485d32
Author: Stephen Sisk <[email protected]>
Date:   2017-04-25T17:36:30Z

    fixup! Add HadoopResourceId

commit c1e6cbcf2360c43b93a33acd65f45204e3c34869
Author: Stephen Sisk <[email protected]>
Date:   2017-04-25T20:49:05Z

    fixup! fixup! Add HadoopResourceId

----


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