[
https://issues.apache.org/jira/browse/FLINK-18054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121499#comment-17121499
]
Sergii Mikhtoniuk commented on FLINK-18054:
-------------------------------------------
I have also noticed some behavioral differences in using {{stopWithSavepoint}}
compared to when running job in a cluster and stopping with CLI.
For example streams created via
{code}
readFile(..., FileProcessingMode.PROCESS_CONTINUOUSLY)
{code}
will incorrectly emit {{MAX_WATERMARK}} when stopping via
{{stopWithSavepoint}}, but will not if stopped via CLI.
> Environment should provide API to resume from savepoint
> -------------------------------------------------------
>
> Key: FLINK-18054
> URL: https://issues.apache.org/jira/browse/FLINK-18054
> Project: Flink
> Issue Type: Improvement
> Components: Test Infrastructure
> Affects Versions: 1.10.1
> Reporter: Sergii Mikhtoniuk
> Priority: Minor
>
> Flink's savepoint API lacks symmetry.
> While you can stop the job with savepoint as:
> {code}
> job.stopWithSavepoint(advanceToEndOfTime, checkpointDir)
> {code}
> ... there is no API to resume from one.
> This make it very hard to test stop-resume functionality as it forces you to
> run a proper cluster and use CLI.
> Workaround:
> To use savepoints in my "unit" tests I'm resorting to subclassing local
> environment and calling {{streamGraphGenerator.setSavepointRestoreSettings}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
