[
https://issues.apache.org/jira/browse/BEAM-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617869#comment-16617869
]
Maximilian Michels commented on BEAM-5396:
------------------------------------------
This is not an easy one. Once the portability is stable, we can start assigning
UUIDs to all the operators and carefully migrate state whenever necessary.
Additionally, we will have to have regression tests to ensure that Beam jobs
can be upgraded from one version to another.
Some background:
https://ci.apache.org/projects/flink/flink-docs-stable/ops/upgrading.html
> Flink portable runner savepoint / upgrade support
> -------------------------------------------------
>
> Key: BEAM-5396
> URL: https://issues.apache.org/jira/browse/BEAM-5396
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Thomas Weise
> Priority: Major
>
> The Flink runner overall and the new portable implementation specifically
> need to support Flink savepoints for production use. Specifically, it should
> be possible to upgrade a stateful portable Beam pipeline that runs on Flink,
> which involves taking a savepoint and then starting the new version of the
> pipeline from that savepoint. The potential issues with pipeline evolution
> and migration are similar to those when using the Flink DataStream API
> (schema / name changes etc.).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
