[
https://issues.apache.org/jira/browse/FLINK-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kostas Kloudas updated FLINK-13123:
-----------------------------------
Release Note: From now on, the {{stop}} command with no further arguments
(gracefully) stops the job with a savepoint at the default savepoint location,
as configured by the user. This changes the semantics of the pre-existing stop
command, as agreed in the mailing list. (was: From now on, the {{stop}}
command with no further arguments (gracefully) stops the job with a savepoint
at the default savepoint location, as configured by the user. This changes the
semantics of the pre-existing stop command, as agreed in the mailing list.
Merged with dafd48893c1adad22ad3ffd7085b6ae481c6cfc7)
> Align Stop/Cancel Commands in CLI and REST Interface and Improve Documentation
> ------------------------------------------------------------------------------
>
> Key: FLINK-13123
> URL: https://issues.apache.org/jira/browse/FLINK-13123
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client, Documentation
> Affects Versions: 1.9.0
> Reporter: Konstantin Knauf
> Assignee: Konstantin Knauf
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the REST API and CLI around stopping and cancelling jobs are not
> aligned in terms of terminology and the differences between {{cancel}} and
> {{job}} are not as clear as they could be.
> I would like to make the following changes to the CLI:
> * add deprecation warning for {{cancel -s}} command and redirect users to
> {{stop}}
> * rename {{-s}} of {{stop}} command to {{-p}} for savepoint location.
> Emphasize that this is optional, as a savepoint is taken in any case
> I would like to make the following changes to the REST API:
> * Rename {{stop-with-savepoint}} to {{stop}}
> * Rename "endOfEventTime" to "drain" in accordance with the CLI
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
