# Creating existing processors in Java for pipeline injection

**URL:** <https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840>\
**Category:** Elasticsearch\
**Created:** [November 30, 2017, 9:27pm UTC](https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840 "2017-11-30T21:27:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fnareva](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@fnareva](https://discuss.elastic.co/u/fnareva)\
**Post date:** [November 30, 2017, 9:27pm UTC](https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840/1 "2017-11-30T21:27:36Z")

</div>

We are currently looking for a good way to create and set processors in our java app.

Is there a JAVA API we are missing for this? Right now we are building the pipeline parameters using XContentBuilder. One suggestion we have is just make implementation of the Processor interface for each processor we want included in the pipeline. E.g. RemoveProcessor. Given that ES ships with those, before we start writing our own implementations we thought we'd ask if there already is a solution for this, besides XContent.

I did go through

> **[Writing Your Own Ingest Processor for Elasticsearch
	  	 | Elastic](https://www.elastic.co/blog/writing-your-own-ingest-processor-for-elasticsearch)**
>
> With Elasticsearch 5.0, a new feature called the ingest node was introduced. To quote the official documentation You can use ingest node to pre-process documents before the actual indexing takes place...

  
but we don't actually need custom processors, just checking whether the XContent is the only good way to inject existing ones.

Thank you.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [December 1, 2017, 8:02am UTC](https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840/2 "2017-12-01T08:02:31Z")

</div>

The classes Elasticsearch ships with are the concrete implementations, not serialized representations.

So you have to use the xcontent builder indeed in order to create pipelines currently.

---

<div class="post-metadata">

**Author:** ![fnareva](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@fnareva](https://discuss.elastic.co/u/fnareva)\
**Post date:** [December 1, 2017, 3:40pm UTC](https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840/3 "2017-12-01T15:40:09Z")

</div>

Thank you.

---

<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:** [December 29, 2017, 3:40pm UTC](https://discuss.elastic.co/t/creating-existing-processors-in-java-for-pipeline-injection/109840/4 "2017-12-29T15:40:55Z")

</div>

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