You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by dhalperi <gi...@git.apache.org> on 2017/05/12 16:22:41 UTC

[GitHub] beam pull request #3121: [BEAM-2277] Add ResourceIdTester and test existing ...

GitHub user dhalperi opened a pull request:

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

    [BEAM-2277] Add ResourceIdTester and test existing ResourceId implementations

    A first cut at some of the parts of the ResourceId spec.
    
    Not expected to pass precommit or review, but would be good to have some eyes on it.
    
    CC: @lukecwik @aviemzur @peihe 

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

    $ git pull https://github.com/dhalperi/beam b2277-resourceid-tester

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

    https://github.com/apache/beam/pull/3121.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 #3121
    
----
commit e258d553ed28f3eb8bc21ddada23c5435e723d92
Author: Dan Halperin <dh...@google.com>
Date:   2017-05-12T16:20:34Z

    [BEAM-2277] Add ResourceIdTester and test existing ResourceId implementations
    
    A first cut at some of the parts of the ResourceId spec.

----


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

[GitHub] beam pull request #3121: [BEAM-2277] Add ResourceIdTester and test existing ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


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