beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-89) DataflowPipelineJob should have an API that prints messages but doesn't wait for completion
Date Fri, 04 Mar 2016 03:06:40 GMT

     [ https://issues.apache.org/jira/browse/BEAM-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Davor Bonaci updated BEAM-89:
-----------------------------
    Component/s:     (was: runner-dataflow)
                 sdk-java-core

> 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: sdk-java-core
>            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)

Mime
View raw message