Assigned
Status Update
No update yet.
Comments
da...@gmail.com
+1
da...@gmail.com
+1
da...@gmail.com
Ten million
nr...@google.com
nr...@google.com
Hello,
This issue report has been forwarded to the Cloud BigQuery Engineering team so that they may investigate it, but there is no ETA for a resolution today. Future updates regarding this issue will be provided here.
This issue report has been forwarded to the Cloud BigQuery Engineering team so that they may investigate it, but there is no ETA for a resolution today. Future updates regarding this issue will be provided here.
ni...@systeme-u.fr
+1 we're touched by this issue too and it's getting really annoying. Example attached
ni...@systeme-u.fr
Attachments 0 and 1 are what we can see in the standard UI i.e misleading estimation. Attachment 2 is the billed volume
a....@n-pg.de
I have the same problem! This is really annoying and costs money.
la...@gmail.com
Hi, can I get read access to the issue mentioned?
Description
Problem you have encountered:
After an update yesterday, BigQuery UI's cost estimation appears to be broken for users who have their language settings configured to use dots as thousands separators. The estimated query processing cost for queries below 1TB are always displayed as
This query will process 0TB when run.. I don`t have a query that could use more than 1TB, so I am unable to check if values larger than 1TB are working correctly. This issue also affects the "query job details" page, where the bytes processed value is displayed as "0 TB" for past queries. However, switching the localization settings to use commas as the thousands separator fixes the issue.What you expected to happen:
Query estimation display values in the correct human readable unit. Example:
This query will process 50.12 MB when run.Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):