[ https://issues.apache.org/jira/browse/FLINK-24275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417544#comment-17417544 ]
Chesnay Schepler commented on FLINK-24275: ------------------------------------------ Which response code would you expect? I assume we want a separate one for the case where the cancellation was already triggered; like 409 because the job was already cancelled? > 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 > Priority: Major > > 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.3.4#803005)