WARNING: Deprecated in 7.15.0.
The Java REST Client is deprecated in favor of the Java API Client.
Deletes an anomaly detection job that exists in the cluster.
DeleteJobRequest object requires a non-null
jobId and can optionally set
The following arguments are optional:
Use to forcefully delete an opened job. This method is quicker than closing
and deleting the job. Defaults to
DeleteJobResponse object indicates the acknowledgement of the job
deletion or the deletion task depending on whether the request was set to wait
When executing a
DeleteJobRequest in the following manner, the client waits
DeleteJobResponse to be returned before continuing with code execution:
DeleteJobResponse deleteJobResponse = client.machineLearning().deleteJob(deleteJobRequest, RequestOptions.DEFAULT);
Synchronous calls may throw an
IOException in case of either failing to
parse the REST response in the high-level REST client, the request times out
or similar cases where there is no response coming back from the server.
In cases where the server returns a
5xx error code, the high-level
client tries to parse the response body error details instead and then throws
ElasticsearchException and adds the original
ResponseException as a
suppressed exception to it.
DeleteJobRequest can also be done in an asynchronous fashion so that
the client can return directly. Users need to specify how the response or
potential failures will be handled by passing the request and a listener to the
asynchronous delete-job method:
The asynchronous method does not block and returns immediately. Once it is
ActionListener is called back using the
if the execution successfully completed or using the
onFailure method if
it failed. Failure scenarios and expected exceptions are the same as in the
synchronous execution case.
A typical listener for
delete-job looks like: