# Enrich processor

**URL:** <https://forum.opensearch.org/t/enrich-processor/7597>\
**Category:** OpenDistro\
**Created:** [November 15, 2021, 10:42am UTC](https://forum.opensearch.org/t/enrich-processor/7597 "2021-11-15T10:42:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![janhoy](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/janhoy/32/1385_2.png) [@janhoy](https://forum.opensearch.org/u/janhoy)\
**Post date:** [November 15, 2021, 10:42am UTC](https://forum.opensearch.org/t/enrich-processor/7597/1 "2021-11-15T10:42:56Z")

</div>

It has been discussed before in [Feature request: enrich processor](https://forum.opensearch.org/t/feature-request-enrich-processor/2108) but that was before OpenSearch was started. As I understand it, ES’s enrich processor is not open source. Are there plans to implement a similar feature for OpenSearch? Would it be API compatible or clean-room effort?

---

<div class="post-metadata">

**Author:** ![searchymcsearchface](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/searchymcsearchface/32/868_2.png) [@searchymcsearchface](https://forum.opensearch.org/u/searchymcsearchface)\
**Post date:** [November 15, 2021, 3:03pm UTC](https://forum.opensearch.org/t/enrich-processor/7597/2 "2021-11-15T15:03:44Z")

</div>

Hey @janhoy - it’s not currently on the roadmap, but there are a lot of ideas that folks have that are yet to be committed to into the roadmap.

As far as APIs, the general ideal is to not worry too much about duplicating APIs from ES. If there is a better way of articulating the API, OpenSearch should work towards that.

---

<div class="post-metadata">

**Author:** ![janhoy](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/janhoy/32/1385_2.png) [@janhoy](https://forum.opensearch.org/u/janhoy)\
**Post date:** [January 21, 2025, 11:52am UTC](https://forum.opensearch.org/t/enrich-processor/7597/3 "2025-01-21T11:52:45Z")

</div>

Just a followup on this. We built a simplified enrich processor for our project, without the intermediate index, since in our use case we’ll use most fields from the source index to enrich from. It works fine, but our plugin is not well suited for contributing back since it evolved over time with custom requirements.