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
@joellabes had a great observation during our call today that the additional functionality of prepending metric names onto secondary calculation aliases could cause the generated dataset to hit the character limits for different data warehouse.
The least permissive of the Big 4 connectors is Postgres with its 59 character limit. The second of these is Redshift with 127 bytes (which I'm assuming is synonymous with characters).
We should add additional testing to confirm whether this fails or not. If it does, we should potentially trim the metric name to the maximum number of characters that can be combined with the secondary calculation alias name.
The text was updated successfully, but these errors were encountered:
callum-mcdata
changed the title
Column Name Lengths - Column Aliasing With Secondary Calcs could break Limit
Column Name Lengths - Column Aliasing With Secondary Calcs Could Break Limit
Jul 11, 2022
Postgres and Redshift already do column name truncation 🤷 . No idea how because that logic isn't encoded into the package so it must be happening in the adapter.
BigQuery and Snowflake are NOT doing this. However their limits are 300 and 250 respectively, so this is less a concern then I had previously thought.
@joellabes had a great observation during our call today that the additional functionality of prepending metric names onto secondary calculation aliases could cause the generated dataset to hit the character limits for different data warehouse.
The least permissive of the Big 4 connectors is Postgres with its 59 character limit. The second of these is Redshift with 127 bytes (which I'm assuming is synonymous with characters).
We should add additional testing to confirm whether this fails or not. If it does, we should potentially trim the metric name to the maximum number of characters that can be combined with the secondary calculation alias name.
The text was updated successfully, but these errors were encountered: