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

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