Delete Filter API
editDelete Filter API
editDelete a machine learning filter.
The API accepts a DeleteFilterRequest
and responds
with a AcknowledgedResponse
object.
Delete Filter Request
editA DeleteFilterRequest
object requires a non-null filterId
.
Delete Filter Response
editThe returned AcknowledgedResponse
object indicates the acknowledgement of the request:
Synchronous execution
editWhen executing a DeleteFilterRequest
in the following manner, the client waits
for the AcknowledgedResponse
to be returned before continuing with code execution:
AcknowledgedResponse response = client.machineLearning().deleteFilter(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 4xx
or 5xx
error code, the high-level
client tries to parse the response body error details instead and then throws
a generic ElasticsearchException
and adds the original ResponseException
as a
suppressed exception to it.
Asynchronous execution
editExecuting a DeleteFilterRequest
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-filter method:
The asynchronous method does not block and returns immediately. Once it is
completed the ActionListener
is called back using the onResponse
method
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-filter
looks like: