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
@NiallRees For the two models in the subject, we need to alias tables like daily_rates, 'stg_usage_in_currency_daily', stg_metering_history, stg_serverless_task_history, and stg_metering_daily_history. As the dbt CI adds the schema name as the prefix to the table name. Referencing columns from these tables breaks the object definition as they defer in the names, having an alias name should fix this.
Please refer to the screenshots:
Tried creating PR to fix this by myself but was not able to commit changes.
The text was updated successfully, but these errors were encountered:
@NiallRees For the two models in the subject, we need to alias tables like
daily_rates
, 'stg_usage_in_currency_daily',stg_metering_history
,stg_serverless_task_history
, andstg_metering_daily_history
. As the dbt CI adds the schema name as the prefix to the table name. Referencing columns from these tables breaks the object definition as they defer in the names, having an alias name should fix this.Please refer to the screenshots:
Tried creating PR to fix this by myself but was not able to commit changes.
The text was updated successfully, but these errors were encountered: