[
https://issues.apache.org/jira/browse/BEAM-5396?focusedWorklogId=171039&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-171039
]
ASF GitHub Bot logged work on BEAM-5396:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Nov/18 10:19
Start Date: 30/Nov/18 10:19
Worklog Time Spent: 10m
Work Description: mxm commented on a change in pull request #7169:
[BEAM-5396] Savepoint restore option in Flink runner
URL: https://github.com/apache/beam/pull/7169#discussion_r237808499
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/FlinkPipelineOptions.java
##########
@@ -204,4 +204,17 @@
ExecutionMode getExecutionModeForBatch();
void setExecutionModeForBatch(ExecutionMode executionMode);
+
+ @Description("Savepoint restore path.")
+ String getSavepointPath();
+
+ void setSavepointPath(String path);
+
+ @Description(
+ "Flag indicating whether non restored state is allowed if the savepoint "
+ + "contains state for an operator that is no longer part of the
pipeline.")
+ @Default.Boolean(false)
Review comment:
Would be nice to test the default in `PipelineOptionstest#testdefaults`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 171039)
Time Spent: 50m (was: 40m)
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)
