[
https://issues.apache.org/jira/browse/BEAM-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179215#comment-15179215
]
Davor Bonaci commented on BEAM-89:
----------------------------------
Yup; waitToFinish() should do just that -- wait until the job finishes. Getting
messages should be orthogonal to this.
This is on the intersection of the core SDK and Dataflow runner. These should
be abstractions available for any job, with specific implementations in each
runner. Thus, I'm changing the component.
> DataflowPipelineJob should have an API that prints messages but doesn't wait
> for completion
> -------------------------------------------------------------------------------------------
>
> Key: BEAM-89
> URL: https://issues.apache.org/jira/browse/BEAM-89
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Eugene Kirpichov
> Assignee: Davor Bonaci
> Priority: Minor
>
> DataflowPipelineJob has a method waitToFinish() that takes a handler for
> printing the job's output messages, AND waits for the job to finish, printing
> messages along the way using that handler.
> However, there are cases when a caller would like to poll for the job's
> messages and print them, but would like to keep the job under the caller's
> control, rather than having to wait for it to complete.
> E.g., one can imagine wanting to do the following "wait until a certain
> Aggregator in the job reaches a certain value, and then cancel the job,
> printing messages along the way". This is not possible with the current API,
> without copying code of waitToFinish().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
