2018-06-04 04:34:55 -04:00
|
|
|
[[java-rest-high-ingest-delete-pipeline]]
|
2018-06-01 08:13:41 -04:00
|
|
|
=== Delete Pipeline API
|
|
|
|
|
2018-06-04 04:34:55 -04:00
|
|
|
[[java-rest-high-ingest-delete-pipeline-request]]
|
2018-06-01 08:13:41 -04:00
|
|
|
==== Delete Pipeline Request
|
|
|
|
|
|
|
|
A `DeletePipelineRequest` requires a pipeline `id` to delete.
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> The pipeline id to delete
|
|
|
|
|
|
|
|
==== Optional arguments
|
|
|
|
The following arguments can optionally be provided:
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-timeout]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> Timeout to wait for the all the nodes to acknowledge the pipeline deletion as a `TimeValue`
|
|
|
|
<2> Timeout to wait for the all the nodes to acknowledge the pipeline deletion as a `String`
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-masterTimeout]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> Timeout to connect to the master node as a `TimeValue`
|
|
|
|
<2> Timeout to connect to the master node as a `String`
|
|
|
|
|
2018-06-04 04:34:55 -04:00
|
|
|
[[java-rest-high-ingest-delete-pipeline-sync]]
|
2018-06-01 08:13:41 -04:00
|
|
|
==== Synchronous Execution
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> Execute the request and get back the response in a `WritePipelineResponse` object.
|
|
|
|
|
2018-06-04 04:34:55 -04:00
|
|
|
[[java-rest-high-ingest-delete-pipeline-async]]
|
2018-06-01 08:13:41 -04:00
|
|
|
==== Asynchronous Execution
|
|
|
|
|
|
|
|
The asynchronous execution of a delete pipeline request requires both the `DeletePipelineRequest`
|
|
|
|
instance and an `ActionListener` instance to be passed to the asynchronous
|
|
|
|
method:
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-async]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> The `DeletePipelineRequest` to execute and the `ActionListener` to use when
|
|
|
|
the execution completes
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
A typical listener for `WritePipelineResponse` looks like:
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-listener]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> Called when the execution is successfully completed. The response is
|
|
|
|
provided as an argument
|
|
|
|
<2> Called in case of failure. The raised exception is provided as an argument
|
|
|
|
|
2018-06-04 04:34:55 -04:00
|
|
|
[[java-rest-high-ingest-delete-pipeline-response]]
|
2018-06-01 08:13:41 -04:00
|
|
|
==== Delete Pipeline Response
|
|
|
|
|
|
|
|
The returned `WritePipelineResponse` allows to retrieve information about the executed
|
|
|
|
operation as follows:
|
|
|
|
|
|
|
|
["source","java",subs="attributes,callouts,macros"]
|
|
|
|
--------------------------------------------------
|
2018-06-04 04:34:55 -04:00
|
|
|
include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-response]
|
2018-06-01 08:13:41 -04:00
|
|
|
--------------------------------------------------
|
|
|
|
<1> Indicates whether all of the nodes have acknowledged the request
|