You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by tgroh <gi...@git.apache.org> on 2016/10/17 23:16:03 UTC

[GitHub] incubator-beam-site pull request #46: Add Blog Post on TestStream

GitHub user tgroh opened a pull request:

    https://github.com/apache/incubator-beam-site/pull/46

    Add Blog Post on TestStream

    The post goes into details on the previous and expanded testing
    infrastructure provided by the Beam SDK and provides examples of the
    times at which elements arrive, and how that impacts the outputs
    produced by a PipelineRunner.

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

    $ git pull https://github.com/tgroh/incubator-beam-site test_stream_blog_post

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

    https://github.com/apache/incubator-beam-site/pull/46.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 #46
    
----
commit ec8f638568f59ac0348c44c763404aa689f7a05f
Author: Thomas Groh <tg...@google.com>
Date:   2016-10-14T00:26:30Z

    Add Blog Post on TestStream
    
    The post goes into details on the previous and expanded testing
    infrastructure provided by the Beam SDK and provides examples of the
    times at which elements arrive, and how that impacts the outputs
    produced by a PipelineRunner.

----


---
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] incubator-beam-site pull request #46: Add Blog Post on TestStream

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

    https://github.com/apache/incubator-beam-site/pull/46


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