# Keyword Type

**URL:** <https://discuss.elastic.co/t/keyword-type/177360>\
**Category:** Elasticsearch\
**Created:** [April 17, 2019, 6:41pm UTC](https://discuss.elastic.co/t/keyword-type/177360 "2019-04-17T18:41:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\
**Post date:** [April 17, 2019, 6:41pm UTC](https://discuss.elastic.co/t/keyword-type/177360/1 "2019-04-17T18:41:40Z")

</div>

I have a application where we are going to do only the aggregations and no search functionality at all. Hence thinking if making all the fields of type keyword instead of text would help me reduce the disk space. Currently I have fields defined as text and keyword type as well.

let me know if that is right approach to do it ?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 17, 2019, 9:33pm UTC](https://discuss.elastic.co/t/keyword-type/177360/2 "2019-04-17T21:33:31Z")

</div>

It should make a difference, yes.

Make sure you are also using `best_compression` 🙂

---

<div class="post-metadata">

**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\
**Post date:** [April 18, 2019, 2:57pm UTC](https://discuss.elastic.co/t/keyword-type/177360/3 "2019-04-18T14:57:09Z")

</div>

thank you 🙂

---

<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:** [May 16, 2019, 2:57pm UTC](https://discuss.elastic.co/t/keyword-type/177360/4 "2019-05-16T14:57:14Z")

</div>

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