# How does Elasticsearch indexes non-text fields

**URL:** <https://discuss.elastic.co/t/how-does-elasticsearch-indexes-non-text-fields/313072>\
**Category:** Elasticsearch\
**Created:** [August 27, 2022, 10:46pm UTC](https://discuss.elastic.co/t/how-does-elasticsearch-indexes-non-text-fields/313072 "2022-08-27T22:46:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 28, 2022, 1:24am UTC](https://discuss.elastic.co/t/how-does-elasticsearch-indexes-non-text-fields/313072/2 "2022-08-28T01:24:02Z")

</div>

Perhaps take a read through this.

`keyword`, numerics `date` etc are not tokenized.. only `text` fields are tokenized

`keyword`s are stored in the inverted index and doc\_values as well

> **[doc\_values | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/doc-values.html)**

Numerics are also stored in the inverted index but with some other meta data to support range searches etc.

> [@How are numeric data types indexed?](https://discuss.elastic.co/t/how-are-numeric-data-types-indexed/187418/2):
>
> There are lots of different mapping types you can use for numeric values, depending on the precision you need. Take a look at [the documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/number.html). The numeric types are optimised for the type of searches you would typically run against a numeric type, like ranges. This means that there is some extra data stored along with the value. If you're not going to be running range queries on the numeric fields and are just storing them for lookup, aggregation or ordering purposes, using a keyword mapping…

---

_[View the full topic](https://discuss.elastic.co/t/how-does-elasticsearch-indexes-non-text-fields/313072)._