You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By replacing some of the current transaction FLOAT types with NUMERIC we avoid any floating point arithmetic issues that we can run into if using BigQuerys FLOAT64.
The text was updated successfully, but these errors were encountered:
No, I think we still need this change. BQ Loader is shipped with schema-ddl 0.9.0 since 0.2.0, which means it creates new columns with NUMERIC type snowplow/iglu#426. Now we need to cherry-pick 8653b16 to reflect this standard atomic events fields.
By replacing some of the current transaction FLOAT types with NUMERIC we avoid any floating point arithmetic issues that we can run into if using BigQuerys FLOAT64.
The text was updated successfully, but these errors were encountered: