# Fielddata

**URL:** <https://discuss.elastic.co/t/fielddata/143172>\
**Category:** Elasticsearch\
**Created:** [August 6, 2018, 1:18pm UTC](https://discuss.elastic.co/t/fielddata/143172 "2018-08-06T13:18:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fram\_Souza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fram_souza/32/24833_2.png) [@Fram\_Souza](https://discuss.elastic.co/u/Fram_Souza)\
**Post date:** [August 6, 2018, 1:18pm UTC](https://discuss.elastic.co/t/fielddata/143172/1 "2018-08-06T13:18:55Z")

</div>

Why do fielddata still exist in new versions of Elasticsearch?

Can not they be discontinued?

Are doc\_values ​​currently unable to replace them?

In what cases are fielddata necessary, since we can use doc\_value in a much more performative way?

---

<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:** [August 6, 2018, 1:35pm UTC](https://discuss.elastic.co/t/fielddata/143172/2 "2018-08-06T13:35:32Z")

</div>

It can be useful when you still need to generate multiple terms from a given text vs indexing the whole text.  
It can be useful when you prefer to pay the cost of memory usage than index space...

So I believe this can be still useful.

---

<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:** [September 3, 2018, 1:35pm UTC](https://discuss.elastic.co/t/fielddata/143172/3 "2018-09-03T13:35:45Z")

</div>

Closed on September 3, 2018, 1:35pm UTC

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