# How are numeric data types indexed?

**URL:** <https://discuss.elastic.co/t/how-are-numeric-data-types-indexed/187418>\
**Category:** Elasticsearch\
**Created:** [June 25, 2019, 7:08pm UTC](https://discuss.elastic.co/t/how-are-numeric-data-types-indexed/187418 "2019-06-25T19:08:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![whatgeorgemade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whatgeorgemade/32/103246_2.png) [@whatgeorgemade](https://discuss.elastic.co/u/whatgeorgemade)\
**Post date:** [June 25, 2019, 8:21pm UTC](https://discuss.elastic.co/t/how-are-numeric-data-types-indexed/187418/2 "2019-06-25T20:21:40Z")

</div>

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 type is more efficient as the extra data isn't generated or stored.

---

_[View the full topic](https://discuss.elastic.co/t/how-are-numeric-data-types-indexed/187418)._
