You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andrés Beck-Ruiz (Jira)" <ji...@apache.org> on 2026/06/10 16:06:00 UTC

[jira] [Updated] (CASSSIDECAR-379) Add PATCH operational-jobs/{id} API to update status of existing operational jobs

     [ https://issues.apache.org/jira/browse/CASSSIDECAR-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrés Beck-Ruiz updated CASSSIDECAR-379:
-----------------------------------------
    Priority: Normal  (was: Major)

> Add PATCH operational-jobs/{id} API to update status of existing operational jobs
> ---------------------------------------------------------------------------------
>
>                 Key: CASSSIDECAR-379
>                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-379
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Sub-task
>            Reporter: Andrés Beck-Ruiz
>            Assignee: Brandon Ho
>            Priority: Normal
>              Labels: CEP-53
>
> In order to enable more operator control over operational jobs, we should add an endpoint for updating the status of operational jobs. This PATCH API is described in more detail [here|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-53%3A+Cassandra+Rolling+Restarts+via+Sidecar#CEP53:CassandraRollingRestartsviaSidecar-PATCH/api/v1/cassandra/operational-jobs/%7Bid%7D] in CEP-53. 
> This will require updates to the {{{}OperationalJobManager{}}}. We should discuss how to ensure that this API is backwards compatible for existing jobs that might not have logic implemented for pausing/aborting operations (eg: throwing a 405 error if unsupported). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org