Pipeline processor
editPipeline processor
editExecutes another pipeline.
Table 28. Pipeline Options
Name | Required | Default | Description |
---|---|---|---|
|
yes |
- |
The name of the pipeline to execute. Supports template snippets. |
|
no |
- |
Conditionally execute this processor. |
|
no |
- |
Handle failures for this processor. See Handling Failures in Pipelines. |
|
no |
|
Ignore failures for this processor. See Handling Failures in Pipelines. |
|
no |
- |
An identifier for this processor. Useful for debugging and metrics. |
{ "pipeline": { "name": "inner-pipeline" } }
The name of the current pipeline can be accessed from the _ingest.pipeline
ingest metadata key.
An example of using this processor for nesting pipelines would be:
Define an inner pipeline:
PUT _ingest/pipeline/pipelineA { "description" : "inner pipeline", "processors" : [ { "set" : { "field": "inner_pipeline_set", "value": "inner" } } ] }
Define another pipeline that uses the previously defined inner pipeline:
PUT _ingest/pipeline/pipelineB { "description" : "outer pipeline", "processors" : [ { "pipeline" : { "name": "pipelineA" } }, { "set" : { "field": "outer_pipeline_set", "value": "outer" } } ] }
Now indexing a document while applying the outer pipeline will see the inner pipeline executed from the outer pipeline:
PUT /my-index/_doc/1?pipeline=pipelineB { "field": "value" }
Response from the index request:
{ "_index": "my-index", "_type": "_doc", "_id": "1", "_version": 1, "result": "created", "_shards": { "total": 2, "successful": 1, "failed": 0 }, "_seq_no": 66, "_primary_term": 1, }
Indexed document:
{ "field": "value", "inner_pipeline_set": "inner", "outer_pipeline_set": "outer" }