# Elasticsearch - JSON date payload being converted to type long, cannot use for range queries

**URL:** <https://discuss.elastic.co/t/elasticsearch-json-date-payload-being-converted-to-type-long-cannot-use-for-range-queries/119552>\
**Category:** Elasticsearch\
**Created:** [February 12, 2018, 9:36pm UTC](https://discuss.elastic.co/t/elasticsearch-json-date-payload-being-converted-to-type-long-cannot-use-for-range-queries/119552 "2018-02-12T21:36:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 12, 2018, 10:05pm UTC](https://discuss.elastic.co/t/elasticsearch-json-date-payload-being-converted-to-type-long-cannot-use-for-range-queries/119552/2 "2018-02-12T22:05:26Z")

</div>

This can not happen. I mean the way you described it can not happen. You should see rejection or something.

Could you provide a full recreation script as described in [About the Elasticsearch category](https://discuss.elastic.co/t/about-the-elasticsearch-category/21). It will help to better understand what you are doing. Please, try to keep the example as simple as possible.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-json-date-payload-being-converted-to-type-long-cannot-use-for-range-queries/119552)._