# Date value interpreted as double

**URL:** <https://discuss.elastic.co/t/date-value-interpreted-as-double/41934>\
**Category:** Elasticsearch\
**Created:** [February 16, 2016, 8:23pm UTC](https://discuss.elastic.co/t/date-value-interpreted-as-double/41934 "2016-02-16T20:23:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![james\_mtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_mtl/32/32330_2.png) [@james\_mtl](https://discuss.elastic.co/u/james_mtl)\
**Post date:** [February 16, 2016, 8:23pm UTC](https://discuss.elastic.co/t/date-value-interpreted-as-double/41934/1 "2016-02-16T20:23:00Z")

</div>

I am indexing documents via the upsert/update function containing a Unix timestamp generated by a Python function. By default, the dynamic mapping interprets this value as a double instead of a date value. If I put a date mapping and then reindex I get a mapping exception error and my index operation fails. I have been looking through the docs and on Stackexchange and I am having a lot of difficulty with this.

---

<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 5, 2017, 11:15pm UTC](https://discuss.elastic.co/t/date-value-interpreted-as-double/41934/2 "2017-07-05T23:15:55Z")

</div>

Closed on July 5, 2017, 11:15pm UTC