[
https://issues.apache.org/jira/browse/FLINK-27419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ingo Bürk updated FLINK-27419:
------------------------------
Description:
The Flink REST API currently offers no endpoint to cancel a triggered
savepoint. This would be useful for clients to make it easier to coordinate the
cleanup of resources.
I propose to add a new `DELETE /jobs/:jobId/savepoints/:triggerId` endpoint
which aborts a triggered and not-yet completed savepoint. If the endpoint is
already completed or failed, this should delete the savepoint and associated
data.
We can probably deprecate the savepoint-disposal endpoint in that case.
was:
The Flink REST API currently offers no endpoint to cancel a triggered
savepoint. This would be useful for clients to make it easier to coordinate the
cleanup of resources.
I propose to add a new `DELETE /jobs/:jobId/savepoints/:triggerId` endpoint
which aborts a triggered and not-yet completed savepoint. If the endpoint is
already completed or failed, this should probably return an error as the API is
built around "triggering savepoints" as a resource, not the savepoint itself,
and thus DELETE would mean canceling the savepoint, not deleting it.
> Endpoint to cancel savepoints
> -----------------------------
>
> Key: FLINK-27419
> URL: https://issues.apache.org/jira/browse/FLINK-27419
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / REST
> Reporter: Ingo Bürk
> Priority: Major
>
> The Flink REST API currently offers no endpoint to cancel a triggered
> savepoint. This would be useful for clients to make it easier to coordinate
> the cleanup of resources.
> I propose to add a new `DELETE /jobs/:jobId/savepoints/:triggerId` endpoint
> which aborts a triggered and not-yet completed savepoint. If the endpoint is
> already completed or failed, this should delete the savepoint and associated
> data.
> We can probably deprecate the savepoint-disposal endpoint in that case.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
