[
https://issues.apache.org/jira/browse/FLINK-21638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21638:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Clean up argument order and semantics of all "stopWithSavepoint" calls in the
> codebase
> --------------------------------------------------------------------------------------
>
> Key: FLINK-21638
> URL: https://issues.apache.org/jira/browse/FLINK-21638
> Project: Flink
> Issue Type: Technical Debt
> Components: Client / Job Submission, Runtime / Coordination
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> This came up in a review:
> https://github.com/apache/flink/pull/14948#discussion_r588304475
> The stopWithSavepoint() methods in Flink have a boolean flag, indicating
> either whether we inject a MAX_WATERMARK in the pipeline, or whether we
> terminate or suspend a job.
> As part of this ticket, I propose to introduce a new enum type in flink-core
> "StopWithSavepointBehavior" with SUSPEND and TERMINATE fields and replace the
> boolean flag with this new field.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
