Retrieves configuration information for anomaly detection jobs in the cluster.
It accepts a
GetJobRequest object and responds with a
GetJobRequest object gets can have any number of
entries. However, they all must be non-null. An empty list is the same as
requesting for all anomaly detection jobs.
Constructing a new request referencing existing
Whether to ignore if a wildcard expression matches no anomaly detection jobs.
Optional boolean value for requesting the job in a format that can then be put into another cluster. Certain fields that can only be set when the job is created are removed.
When executing a
GetJobRequest in the following manner, the client waits
GetJobResponse to be returned before continuing with code execution:
GetJobResponse response = client.machineLearning().getJob(request, 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.
GetJobRequest 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 get-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
get-job looks like: