# \[Just Pushed\] Terms API now supports numbers/dates

**URL:** <https://discuss.elastic.co/t/just-pushed-terms-api-now-supports-numbers-dates/2857>\
**Category:** Elasticsearch\
**Created:** [March 22, 2010, 12:38am UTC](https://discuss.elastic.co/t/just-pushed-terms-api-now-supports-numbers-dates/2857 "2010-03-22T00:38:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 22, 2010, 12:38am UTC](https://discuss.elastic.co/t/just-pushed-terms-api-now-supports-numbers-dates/2857/1 "2010-03-22T00:38:58Z")

</div>

The terms API supported only strings. Numbers and dates were basically not  
supported with the only workaround is the use a multi field mapper, with a  
string type for them as well as number. But, even that is not good enough,  
since they are treated as text, so, for example, the from/to are not that  
meaningful (1, 11, 2, ...).

Now, the terms API fully supports numbers and dates, both when using  
from/to, and returning the actual values. See here:  
[http://github.com/elasticsearch/elasticsearch/issues/issue/78](http://github.com/elasticsearch/elasticsearch/issues/issue/78).

As a side note, the terms API is one of my favorite APIs. You can easily  
show tag clouds, breakdown of "heat map" of different documents in the  
index, for example, based on specific date or something similar.

-shay.banon

---

<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:** [July 6, 2017, 4:25am UTC](https://discuss.elastic.co/t/just-pushed-terms-api-now-supports-numbers-dates/2857/2 "2017-07-06T04:25:11Z")

</div>

Closed on July 6, 2017, 4:25am UTC


