# Improve support for Master Data and Enrichment

**URL:** <https://discuss.elastic.co/t/improve-support-for-master-data-and-enrichment/377284>\
**Category:** Kibana\
**Created:** [April 18, 2025, 1:49pm UTC](https://discuss.elastic.co/t/improve-support-for-master-data-and-enrichment/377284 "2025-04-18T13:49:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![catn0b0t](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catn0b0t/32/122758_2.png) [@catn0b0t](https://discuss.elastic.co/u/catn0b0t)\
**Post date:** [April 18, 2025, 1:49pm UTC](https://discuss.elastic.co/t/improve-support-for-master-data-and-enrichment/377284/1 "2025-04-18T13:49:28Z")

</div>

If you are setting up anything that looks like a datawarehouse or whatever, sooner or later you are going to have a need for some kind of "lookup tables". The lack of support for such thing in Kibana is really frustrating. This need is not something farefetched or exotic, it's like pretty basic stuff so I really can't understand that this is not included in an enterprise product like Elastic-Kibana.  
Currently there is the "Enrich" processor in pipelines (which only has basic documentation) which needs an "Enrichment Policy" to work. This Enrichment Policy is basically a lookup table. But then again

- There is no UI in Kibana to create/manage these. Why?
- After you have create the Enrichment Policy, each time the data in the source index changes you need to update the Enrichment Policy. Then why can't this be a continuous "Latest"-type transformation?

So, lot's of questions concerning a lacking feature which I'd consider to be standard stuff for any data platform.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [April 18, 2025, 3:03pm UTC](https://discuss.elastic.co/t/improve-support-for-master-data-and-enrichment/377284/2 "2025-04-18T15:03:56Z")

</div>

Yeah, doing enrichments with only Elasticsearch can be complicated, there is still a lot of things to be improved.

There were improvements on doing enrichments during query time when using ESQL, but not much changed for doing enrichments during ingestion time.

This is one of the reasons for why Logstash is still required, you can easily do enrichments on Logstash during ingestion.

> [@catn0b0t](#):
>
> After you have create the Enrichment Policy, each time the data in the source index changes you need to update the Enrichment Policy. Then why can't this be a continuous "Latest"-type transformation?

There is an open issue about allowing Scheduling the execution of Enrichment policies here: [Enrich processor: allow scheduling of policy executions · Issue #50071 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/50071)

---

<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:** [April 18, 2025, 3:15pm UTC](https://discuss.elastic.co/t/improve-support-for-master-data-and-enrichment/377284/3 "2025-04-18T15:15:09Z")

</div>

> [@catn0b0t](#):
>
> There is no UI in Kibana to create/manage these.

There's one. Under index management IIRC.

> [@catn0b0t](#):
>
> - After you have create the Enrichment Policy, each time the data in the source index changes you need to update the Enrichment Policy. Then why can't this be a continuous "Latest"-type transformation?

That's what ES|QL LOOKUP JOIN does from 8.18.