[
https://issues.apache.org/jira/browse/FLINK-24275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490322#comment-17490322
]
Chesnay Schepler commented on FLINK-24275:
------------------------------------------
IMO we should only document things (in particular in the open api spec) if we
can enforce&guarantee it in some way, which currently isn't possible due to
technical limitations. This improvement is tracked in
https://issues.apache.org/jira/browse/FLINK-26045.
Instead we noted it in the release notes.
> Allow idempotent job cancellation
> ---------------------------------
>
> Key: FLINK-24275
> URL: https://issues.apache.org/jira/browse/FLINK-24275
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Reporter: Austin Cawley-Edwards
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> As a user of Flink, I want to be able to cancel a job from an external system
> in a fault-tolerant way without guessing if the job has already been
> cancelled.
>
> Currently, the cancel endpoint (PATCH /jobs/:jobid?mode=cancel) will return a
> 404 if the job is already cancelled. This makes it hard to detect if the job
> truly doesn't exist, or if it is already in the desired state.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
