[jira] [Commented] (BEAM-443) PipelineResult needs waitToFinish() and cancel()

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user peihe opened a pull request:

    https://github.com/apache/incubator-beam/pull/1097

    [BEAM-443] Update Beam batch examples to call waitUntilFinish()

    
    


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

    $ git pull https://github.com/peihe/incubator-beam waitInExample

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

    https://github.com/apache/incubator-beam/pull/1097.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 #1097
    
----
commit 6ac9e9930208dfdf0789a066243048e5a01c9f5e
Author: Pei He <pe...@google.com>
Date:   2016-10-13T21:44:13Z

    [BEAM-443] Update Beam batch examples to call waitUntilFinish()

----


> PipelineResult needs waitToFinish() and cancel()
> ------------------------------------------------
>
>                 Key: BEAM-443
>                 URL: https://issues.apache.org/jira/browse/BEAM-443
>             Project: Beam
>          Issue Type: New Feature
>            Reporter: Pei He
>            Assignee: Pei He
>             Fix For: 0.2.0-incubating
>
>
> waitToFinish() and cancel() are two most common operations for users to interact with a started pipeline.
> Right now, they are only available in DataflowPipelineJob. But, it is better to move them to the common interface, so people can start implement them in other runners, and runner agnostic code can interact with PipelineResult better.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)