1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980 |
- [[java-rest-high-ingest-delete-pipeline]]
- === Delete Pipeline API
- [[java-rest-high-ingest-delete-pipeline-request]]
- ==== Delete Pipeline Request
- A `DeletePipelineRequest` requires a pipeline `id` to delete.
- ["source","java",subs="attributes,callouts,macros"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request]
- --------------------------------------------------
- <1> The pipeline id to delete
- ==== Optional arguments
- The following arguments can optionally be provided:
- ["source","java",subs="attributes,callouts,macros"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-timeout]
- --------------------------------------------------
- <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"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-request-masterTimeout]
- --------------------------------------------------
- <1> Timeout to connect to the master node as a `TimeValue`
- <2> Timeout to connect to the master node as a `String`
- [[java-rest-high-ingest-delete-pipeline-sync]]
- ==== Synchronous Execution
- ["source","java",subs="attributes,callouts,macros"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute]
- --------------------------------------------------
- <1> Execute the request and get back the response in a `WritePipelineResponse` object.
- [[java-rest-high-ingest-delete-pipeline-async]]
- ==== 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"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-async]
- --------------------------------------------------
- <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"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-execute-listener]
- --------------------------------------------------
- <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
- [[java-rest-high-ingest-delete-pipeline-response]]
- ==== Delete Pipeline Response
- The returned `WritePipelineResponse` allows to retrieve information about the executed
- operation as follows:
- ["source","java",subs="attributes,callouts,macros"]
- --------------------------------------------------
- include-tagged::{doc-tests}/IngestClientDocumentationIT.java[delete-pipeline-response]
- --------------------------------------------------
- <1> Indicates whether all of the nodes have acknowledged the request
|