cancel-connector-sync-job-api.asciidoc 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. [[cancel-connector-sync-job-api]]
  2. === Cancel connector sync job API
  3. ++++
  4. <titleabbrev>Cancel connector sync job</titleabbrev>
  5. ++++
  6. preview::[]
  7. Cancels a connector sync job.
  8. [[cancel-connector-sync-job-api-request]]
  9. ==== {api-request-title}
  10. `PUT _connector/_sync_job/<connector_sync_job_id>/_cancel`
  11. [[cancel-connector-sync-job-api-prereqs]]
  12. ==== {api-prereq-title}
  13. * To sync data using connectors, it's essential to have the Elastic connectors service running.
  14. * The `connector_sync_job_id` parameter should reference an existing connector sync job.
  15. [[cancel-connector-sync-job-api-desc]]
  16. ==== {api-description-title}
  17. Cancels a connector sync job, which sets the `status` to `cancelling` and updates `cancellation_requested_at` to the current time.
  18. The connector service is then responsible for setting the `status` of connector sync jobs to `cancelled`.
  19. [[cancel-connector-sync-job-api-path-params]]
  20. ==== {api-path-parms-title}
  21. `connector_sync_job_id`::
  22. (Required, string)
  23. [[cancel-connector-sync-job-api-response-codes]]
  24. ==== {api-response-codes-title}
  25. `200`::
  26. Connector sync job cancellation was successfully requested.
  27. `404`::
  28. No connector sync job matching `connector_sync_job_id` could be found.
  29. [[cancel-connector-sync-job-api-example]]
  30. ==== {api-examples-title}
  31. The following example cancels the connector sync job with ID `my-connector-sync-job-id`:
  32. [source,console]
  33. ----
  34. PUT _connector/_sync_job/my-connector-sync-job-id/_cancel
  35. ----
  36. // TEST[skip:there's no way to clean up after creating a connector sync job, as we don't know the id ahead of time. Therefore, skip this test.]