# Elasticsearch data dictionary

**URL:** <https://discuss.elastic.co/t/elasticsearch-data-dictionary/85440>\
**Category:** Elasticsearch\
**Created:** [May 11, 2017, 3:35pm UTC](https://discuss.elastic.co/t/elasticsearch-data-dictionary/85440 "2017-05-11T15:35:50Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![eirc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eirc/32/11769_2.png) [@eirc](https://discuss.elastic.co/u/eirc)\
**Post date:** [May 14, 2017, 1:59pm UTC](https://discuss.elastic.co/t/elasticsearch-data-dictionary/85440/5 "2017-05-14T13:59:07Z")

</div>

Uhmm which one makes sense? The mappings support, the plugin or \_meta for fields?

I started looking around for info regarding Kibana plugins and it seems that messing around with the Discover app's UI will have some caveats as mentioned in this [thread](https://discuss.elastic.co/t/inject-front-end-code-into-discover-from-custom-plugin/72871). I'm still not sure though, so I'll probably have to look more into how they work.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-data-dictionary/85440)._