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
Runtime Error intest elementary_column_anomalies_fact_table_null_count__missing_count__average__success_count (models/marts/fact_table.yml)
Relation name '"test_7ffaec620b_elementary_column_anomalies_fact_table_null_count__missing_count__av__metrics__tmp_20240423000522692548"' is longer than 127 characters
Expected behavior
Tests run successfully and elementary is able to create temp tables
Environment (please complete the following information):
dbt package Version: 0.14.1
Additional context
dbt running in prod redshift
The text was updated successfully, but these errors were encountered:
It looks like the problem is it's adding both single and double quotes. the relation name '"<table_name>"' is longer than 127 characters is accurate as it's actually 129 characters. changing this line to 125 fixes it.
MiConnell
added a commit
to MiConnell/dbt-data-reliability
that referenced
this issue
Apr 23, 2024
Hi @MiConnell !
Thanks for opening this issue and the associated PR, and sorry for the delayed response.
I believe the double quoting is likely a bug here, but nonetheless I don't see an issue with reducing the number of characters to 125 for now so I'm going to approve and merge it.
Describe the bug
elementary
column_anomalies
tests are unable to run on Redshift due to table naming length restrictionsTo Reproduce
Steps to reproduce the behavior:
elementary.column_anomalies
tests to columns in a dbt model that builds in Redshiftdbt test -s my_model
error occurs:
Expected behavior
Tests run successfully and elementary is able to create temp tables
Environment (please complete the following information):
Additional context
dbt running in prod redshift
The text was updated successfully, but these errors were encountered: