[
https://issues.apache.org/jira/browse/BEAM-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609642#comment-15609642
]
Pei He edited comment on BEAM-443 at 10/26/16 9:07 PM:
-------------------------------------------------------
reopen the jira because there are more discussions about:
1. whether waitUntilFinish should throw exceptions.
2. whether it should throw checked or unchecked exceptions.
There is no consensus. But, the best option for now is to make waitUntilFinish
throw RuntimeException. So, the example code and most users main() don't need
to either try-catch around waitUntilFinish or declare throws Exception
everywhere.
was (Author: pei...@gmail.com):
reopen the jira because there are more discussions about:
1. whether waitUntilFinish should throw exceptions.
2. whether it should throw checked or unchecked exceptions.
> PipelineResult needs waitUntilFinish() 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)
