Stops one or more data frame analytics jobs.
This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.
If the Elasticsearch security features are enabled, you must have the following built-in roles or equivalent privileges:
A data frame analytics job can be started and stopped multiple times throughout its lifecycle.
You can stop multiple data frame analytics jobs in a single API request by using a comma-separated list of data frame analytics jobs or a wildcard expression. You can stop all data frame analytics job by using _all or by specifying * as the <data_frame_analytics_id>.
- (Required, string) Identifier for the data frame analytics job. This identifier can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and underscores. It must start and end with alphanumeric characters.
(Optional, boolean) Specifies what to do when the request:
- Contains wildcard expressions and there are no data frame analytics jobs that match.
_allstring or no identifiers and there are no matches.
- Contains wildcard expressions and there are only partial matches.
The default value is
true, which returns an empty
data_frame_analyticsarray when there are no matches and the subset of results when there are partial matches. If this parameter is
false, the request returns a
404status code when there are no matches or only partial matches.
- (Optional, boolean) If true, the data frame analytics job is stopped forcefully.
- (Optional, time units) Controls the amount of time to wait until the data frame analytics job stops. Defaults to 20 seconds.