# Chaining ingest pipelines?

**URL:** https://discuss.elastic.co/t/chaining-ingest-pipelines/96010
**Category:** Elasticsearch
**Created:** [August 6, 2017, 10:23am UTC](https://discuss.elastic.co/t/chaining-ingest-pipelines/96010 "2017-08-06T10:23:16Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Dan\_Markhasin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_markhasin/32/14187_2.png) [@Dan\_Markhasin](https://discuss.elastic.co/u/Dan_Markhasin)
#### Post date: [August 6, 2017, 10:23am UTC](https://discuss.elastic.co/t/chaining-ingest-pipelines/96010/1 "2017-08-06T10:23:17Z")

</div>

Is it possible to chain ingest pipelines or create some sort of relationship between them?  
For example, I would like to perform some calculations/modifications on all incoming documents, and then perform some business specific logic for some of the documents.

I don't want to have to copy the global logic to each and every pipeline - is there a way to "include" a pipeline in another pipeline? Or specify more than one pipeline via the API?

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [August 6, 2017, 11:26am UTC](https://discuss.elastic.co/t/chaining-ingest-pipelines/96010/2 "2017-08-06T11:26:53Z")

</div>

No but that could be a nice feature request to add IMO.

Like an ingest ingest processor.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 3, 2017, 11:27am UTC](https://discuss.elastic.co/t/chaining-ingest-pipelines/96010/3 "2017-09-03T11:27:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
