# Long JSON number lost precision

**URL:** <https://discuss.elastic.co/t/long-json-number-lost-precision/72124>\
**Category:** Elasticsearch\
**Created:** [January 19, 2017, 7:11am UTC](https://discuss.elastic.co/t/long-json-number-lost-precision/72124 "2017-01-19T07:11:33Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\
**Post date:** [January 24, 2017, 12:03pm UTC](https://discuss.elastic.co/t/long-json-number-lost-precision/72124/12 "2017-01-24T12:03:42Z")

</div>

Ahh, I see ... so something in Kibana's dev console is maybe truncating the long value. I assume a workaround here is for you to make this long value a string instead?

Can you open a Kibana issue, linking to this discussion? Thanks.

Mike McCandless

---

_[View the full topic](https://discuss.elastic.co/t/long-json-number-lost-precision/72124)._