RonBarkan commented on issue #20106:
URL: https://github.com/apache/beam/issues/20106#issuecomment-1872327065
Running a pipeline, then running another pipeline or even just some bit of
non-pipeline code, when the first is finished, is not possible with this
behavior.
Why is this important / valid use case:
1. Many pipelines end in writing some output somewhere as a terminal state,
so you cannot chain another step past it. However, if you want to do something,
such as write a marker file, after all output has completed, you must do it
after the pipeline ends.
You can only do this if you `waitUntilFinish()`.
2. If you collect metrics from the run to store them or process them in some
way, you probably want to:
```
var result = pipeline.run();
result.waitUntilFinish();
processMetrics(result.metrics());
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
