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
Describe the bug
All our anomaly checks are raising column "metric_type" does not exist in data_monitoring_metrics during dbt test after upgrading to dbt 0.16.0.
[2024-08-13, 10:28:03 UTC] {pod_manager.py:447} INFO - [base] Database Error in test elementary_all_columns_anomalies_slv_events_document_analytics_ (models/silver/events/production/events.yml)
[2024-08-13, 10:28:03 UTC] {pod_manager.py:447} INFO - [base] column "metric_type" does not exist in data_monitoring_metrics
Expected behavior
That the anomaly tests runs simply successfully, as on former versions.
Screenshots
The columns in data_monitoring_metrics, closest to metric_type being metric_name
Environment (please complete the following information):
Elementary CLI (edr) version: Irrelevant
Elementary dbt package version: 0.16.0
dbt version you're using: 1.8.3
Data warehouse: Redshift
Infrastructure details: "Production" nightly dbt run + dbt test ran from Airflow in k8s pod.
Additional context
To clarify, dbt deps + dbt run -s elementary has been ran before running dbt test on version 0.16.0
Would you be willing to contribute a fix for this issue?
Not sure if that would be the most pragmatic approach :)
The text was updated successfully, but these errors were encountered:
Hi @henriklaurentz !
Can you please clarify if the dbt run -s elementary runs were executed on the same dbt profile as your production environment?
Because this should fix the issue (we indeed added a field to data_monitoring_metrics)
Describe the bug
All our anomaly checks are raising
column "metric_type" does not exist in data_monitoring_metrics
duringdbt test
after upgrading to dbt 0.16.0.To Reproduce
Steps to reproduce the behavior:
1.Apply some "model level" tests
dbt test
Expected behavior
That the anomaly tests runs simply successfully, as on former versions.
Screenshots
The columns in
data_monitoring_metrics
, closest tometric_type
beingmetric_name
Environment (please complete the following information):
dbt run
+dbt test
ran from Airflow in k8s pod.Additional context
To clarify,
dbt deps
+dbt run -s elementary
has been ran before runningdbt test
on version0.16.0
Would you be willing to contribute a fix for this issue?
Not sure if that would be the most pragmatic approach :)
The text was updated successfully, but these errors were encountered: