Hi <!channel>,
:small_red_triangle: We have found...
# generalo
Or Avidov
05/17/2022, 5:33 PMHi <!channel>,
🔺 We have found today a small configuration issue that may cause losing history of alerts when running our models again after running the tests.
The solution is very easy and doesn't require code / package update, so if you already deployed Elementary please just do the following 2 steps -
1. In your dbt_project.yml under 'elementary' remove '+materialized: table'
2. Run -
Copy code
dbt run -s filtered_information_schema_columns filtered_information_schema_tables monitors_runs anomaly_threshold_sensitivity metrics_anomaly_score model_run_results test_run_results --full-refresh👍 4
Or Avidov
05/17/2022, 5:34 PMMore context -
In dbt materializations are applied hierarchically. For example when you configure your default materialization in the project level to be 'view' and you have a model that is defined with materialization of 'table', this model configuration will take precedence over the project level configuration (the more granular configuration always wins).
Or Avidov
05/17/2022, 5:35 PMThat being said, we have learned today that if the materialization for a package is defined in the main dbt_project.yml (meaning not in the package's dbt_project.yml) then it overrides the granular materialization configuration that is defined in the package's models. We think that this is related to the order macros are defined between project and imported packages in dbt (materialization is essentially a macro).
Or Avidov
05/17/2022, 5:35 PMThis was a configuration issue and we already updated our documentation accordingly.
Or Avidov
05/17/2022, 5:37 PMPlease feel free to reach out if you have any questions about it 🙏