# Alternative for Enrich Processor

**URL:** <https://forum.opensearch.org/t/alternative-for-enrich-processor/11201>\
**Category:** OpenSearch\
**Tags:** feature-request\
**Created:** [October 13, 2022, 1:38am UTC](https://forum.opensearch.org/t/alternative-for-enrich-processor/11201 "2022-10-13T01:38:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![groge](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@groge](https://forum.opensearch.org/u/groge)\
**Post date:** [October 13, 2022, 1:38am UTC](https://forum.opensearch.org/t/alternative-for-enrich-processor/11201/1 "2022-10-13T01:38:24Z")

</div>

Hi,  
I’m trying to move from logstash to OpenSearch ingest, but the lack of a “translate” feature is the biggest stumbling block.  
Elasticsearch has an alternative function called “enrich”, any plan for alternative function for “translate”?

There have been similar requests like below before, but no updates for a long time

> [@Enrich processor](https://forum.opensearch.org/t/enrich-processor/7597):
>
> 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?

> [@Ingest pipelines support](https://forum.opensearch.org/t/ingest-pipelines-support/7716):
>
> How are ingest pipelines supported in OpenSearch? What types of processors can I use? Is it possible to use enrich processor?