Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Not A Problem
-
2.19.0, 2.20.0
-
None
Description
The Flink 1.9/1.10 web interface is missing the Stop button for a streaming pipeline, which is pretty useful to drain a streaming pipeline.
For example to be able to cleanly shutdown a pipeline when a feature is going to be released tomorrow, and the pipeline processing code should be updated before, without the overhead of re-reading the complete past. Taking a snapshot uses the current representation of the Beam code as a Flink job, but what if one wants to update the Beam code and thus the pipeline code without the need to reprocess the whole history? Moreover, a stop button is very useful when a new Flink version is going to be rolled out: then one can drain all pipelines, rollout a new Flink version and start them at the point where they left off with their last committed offset in Kafka.
