WARNING: Version 6.0 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
The delete job API enables you to delete an existing anomaly detection job.
All job configuration, model state and results are deleted.
Deleting a job must be done via this API only. Do not delete the
job directly from the .ml-*
indices using the Elasticsearch
DELETE Document API. When X-Pack security is enabled, make sure no write
privileges are granted to anyone over the .ml-*
indices.
Before you can delete a job, you must delete the datafeeds that are associated
with it. See Delete Datafeeds. Unless the force
parameter
is used the job must be closed before it can be deleted.
It is not currently possible to delete multiple jobs using wildcards or a comma separated list.
-
job_id
(required) - (string) Identifier for the job
You must have manage_ml
, or manage
cluster privileges to use this API.
For more information, see Security Privileges.