Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kibana incorrectly rounds values larger than 2^53 #7863

Closed
w33ble opened this issue Jul 27, 2016 · 5 comments
Closed

Kibana incorrectly rounds values larger than 2^53 #7863

w33ble opened this issue Jul 27, 2016 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@w33ble
Copy link
Contributor

w33ble commented Jul 27, 2016

Kibana version: Any

Elasticsearch version: Any

Description of the problem including expected versus actual behavior:
Elasticsearch output is being parsed by Javascript, which has a number limit of 2^53 (9,007,199,254,740,992). Numbers larger than that are cast to doubles, and their value is shown incorrectly.

This is currently caused by the Ace editor parsing the data before displaying it. The solution will need to involve skipping that output parsing somehow.

@w33ble w33ble added bug Fixes for quality problems that affect the customer experience Feature:Console Dev Tools Console Feature labels Jul 27, 2016
@w33ble
Copy link
Contributor Author

w33ble commented Aug 2, 2016

This happens anywhere the JSON data is being parsed, like in both tabs in the document view (see bytes, value should be 111111111111111111):

screenshot 2016-08-02 13 42 26

screenshot 2016-08-02 13 44 09

@w33ble w33ble removed the Feature:Console Dev Tools Console Feature label Aug 2, 2016
@w33ble w33ble changed the title Console can't display output values larger than 2^53 Kibana incorrectly rounds values larger than 2^53 Aug 2, 2016
@rlueckl
Copy link

rlueckl commented Aug 4, 2016

We encountered the same problem, it would be great if this got fixed!

@jakauppila
Copy link

+1

@Bargs
Copy link
Contributor

Bargs commented Feb 7, 2017

Another existing ticket here #1274

@w33ble I think these are reporting the same thing, should we close this in favor of the older ticket?

@w33ble
Copy link
Contributor Author

w33ble commented Feb 8, 2017

@Bargs yeah, these do in fact look like the same issue. Thanks, closing.

@w33ble w33ble closed this as completed Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

4 participants