Bug reports

allenhe999 · September 28, 2023, 2:15am

allenhe999 · September 28, 2023, 2:16am

and when i tap 62146624513159168 in the filter use "is", it automatic turn to 62146624513159120

Luiggi · September 28, 2023, 3:05pm

github.com/metabase/metabase

Floating-point rounding errors in UI for very large integers (JS stores all numbers as 64-bit floats)

opened 08:56AM - 25 Aug 17 UTC

bcbob

Type:Bug Priority:P1 .Correctness Difficulty:Hard .Frontend .Backend Querying/GUI

Our data has several primary / foreign key ID fields that are 8 byte BIGINT's. …So fairly large numbers, many above 256^7, are involved. Metabase is unable to display the large numbers as answers, and appears to round them off when displaying them. Among other issues, this creates problems with foreign key links. The underlying data is correct - and downloading the answer as a CSV yields the correct numbers, without an apparent rounding error. It is not possible to drill through the data, because Metabase appears to use the displayed number (rather than the actual query result as shown in the CSV download) to make the link / drill down. The result is an error screen when drilling down for linked foreign key records. The following screen shots show the problem: 1. THE QUESTION RESULT DOWNLOADED AS A CSV, showing the correct large numbers: ![image](https://user-images.githubusercontent.com/30799811/29706747-32c90dc4-8983-11e7-8f7a-722d13ddd061.png) 2. THE QUESTION RESULT DISPLAYED ON SCREEN, showing the apparently rounded numbers: ![image](https://user-images.githubusercontent.com/30799811/29706803-6299142c-8983-11e7-9f73-8f036a5404ba.png) 3. And the normal error screen when attempting to drill down / click through on the rounded numbers: ![image](https://user-images.githubusercontent.com/30799811/29706857-8f7327b2-8983-11e7-8431-8667137859f1.png) ⬇️ **Please click the 👍 reaction instead of leaving a `+1` or 👍 comment**