You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2018/11/29 06:50:00 UTC
[jira] [Updated] (BEAM-5396) Flink portable runner savepoint /
upgrade support
[ https://issues.apache.org/jira/browse/BEAM-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Weise updated BEAM-5396:
-------------------------------
Description: The portable Flink runner needs to support Flink savepoints for production use. 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.). (was: 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.).)
> 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
> Assignee: Thomas Weise
> Priority: Major
> Labels: portability, portability-flink
>
> The portable Flink runner needs to support Flink savepoints for production use. 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)