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

Pei He closed BEAM-444.
-----------------------
       Resolution: Won't Fix
    Fix Version/s: Not applicable

Obsolete given users can control blocking run with PipelineResult.

> Promote isBlockOnRun() to PipelineOptions.
> ------------------------------------------
>
>                 Key: BEAM-444
>                 URL: https://issues.apache.org/jira/browse/BEAM-444
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Pei He
>            Assignee: Pei He
>             Fix For: Not applicable
>
>
> Currently, blockOnRun is implemented in different ways by runners.
> DirectRunner did blockOnRun based on DirectOptions.isBlockOnRun.
> Dataflow have a separate BlockingDataflowRunner.
> Flink and Spark runners might or might not block depends on their 
> implementation on run().
> I think DirectRunner's approach is the right way to go, and isBlockOnRun 
> options need to be promoted to the general PipelineOptions.



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

Reply via email to