# Type: long fields show wrong values in kibana **URL:** \ **Category:** Kibana\ **Created:** [December 29, 2022, 12:16pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154 "2022-12-29T12:16:11Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![nisow95612](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@nisow95612](https://discuss.elastic.co/u/nisow95612)\ **Post date:** [December 29, 2022, 12:16pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/1 "2022-12-29T12:16:11Z")
Hello, I have noticed a problem with Kibana. Values with `"type": "long"` do not display correctly. For example let's take the value "1 671 607 837 241 650 **688**" displayed in Discover: ![InDiscoverOverview](https://us1.discourse-cdn.com/elastic/original/3X/8/5/85496431e83bf6802a7478f071aac78d3a3234c4.png) ![InDiscoverDetail](https://us1.discourse-cdn.com/elastic/original/3X/f/d/fda7d3e0e03525e42eea140c701c899e9c88f375.png) This is wrong. When I swith to JSON, I see ES returned "1671607837241650 **700**". EDIT: Oh. I see that's also wrong, because \_source was "1671607837241650 **580**". ```auto { "_index": "myindex", "_type": "_doc", "_id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa", "_version": 1, "_score": 1, "_source": { "aaaaa": 123456, "eventtime": "1671607837241650580", "zzzzz": "abcdef" }, "fields": { "aaaaa": [ 123456 ], "eventtime": [ 1671607837241650700 ], "zzzzz": [ "abcdef" ] } } ``` I tested this using latest ES 7.17 - can't go to 8 until I replace/fix software that went opensearch ☹ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 29, 2022, 12:19pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/2 "2022-12-29T12:19:28Z")
OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance. (This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: ) ---
**Author:** ![nisow95612](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@nisow95612](https://discuss.elastic.co/u/nisow95612)\ **Post date:** [December 29, 2022, 12:29pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/3 "2022-12-29T12:29:48Z")
Thank you. I rephrased it so its obvious my problem is with ES and that I am staying with ES. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [December 29, 2022, 1:10pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/4 "2022-12-29T13:10:05Z")
This is related to the maximum precision of JavaScript, check this [closed issue](https://github.com/elastic/kibana/issues/10055) and also this [issue](https://github.com/elastic/kibana/issues/1274) on Github. If you are using `eventtime` just for display, you may change the mapping to `keyword`. ---
**Author:** ![nisow95612](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@nisow95612](https://discuss.elastic.co/u/nisow95612)\ **Post date:** [December 29, 2022, 1:46pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/5 "2022-12-29T13:46:38Z")
Thank you for the quick reply. I wonder why I failed to find it. Do you also happen why is `fields.eventtime` rounded in JSON? I captured traffic and verified that it really happened on the wire. I don't see any purpose to ES returning "wrong" values like that. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [December 29, 2022, 1:53pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/6 "2022-12-29T13:53:43Z")
> [@nisow95612](#): > > I don't see any purpose to ES returning "wrong" values like that. It is not ES that is returning the wrong value, it is Kibana. The `fields` object is created by Kibana using the Fields API, it only exists in the Kibana response. ---
**Author:** ![nisow95612](https://avatars.discourse-cdn.com/v4/letter/n/3d9bf3/32.png) [@nisow95612](https://discuss.elastic.co/u/nisow95612)\ **Post date:** [December 29, 2022, 2:08pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/7 "2022-12-29T14:08:56Z")
Oh, right. That response comes from Kibana API, not ES API. When I read " [64 bit number/integer support in Kibana · Issue #40183 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/40183) " very carefully, it turns out it describes all of these issues already. When you said it's Javascripts fault, I (incorrectly) assumed that only the browser part of Kibana will be affected. Does this mean there is Javascript on the Kibana server? Thank you for bearing _with_ me & I wish a happy new year to you. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [December 29, 2022, 2:13pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/8 "2022-12-29T14:13:53Z")
> [@nisow95612](#): > > Does this mean there is Javascript on the Kibana server? Yes, Kibana is built on Node, so it is built on JavaScript. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 26, 2023, 2:14pm UTC](https://discuss.elastic.co/t/type-long-fields-show-wrong-values-in-kibana/322154/9 "2023-01-26T14:14:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.