Hello, We have recently upgraded to elementary v0.14.0, and we see these failures now:

[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base] [0m05:47:12    Compilation Error in model dbt_exposures (models/edr/dbt_artifacts/dbt_exposures.sql)
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base] 
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                 The source and target schemas on this incremental model are out of sync!
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                 They can be reconciled in several ways:
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                   - set the `on_schema_change` config to either append_new_columns or sync_all_columns, depending on your situation.
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                   - Re-run the incremental model with `full_refresh: True` to update the target schema.
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                   - update the schema manually and re-run the process.
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base] 
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                 Additional troubleshooting context:
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                    Source columns not in target: [<BigQueryColumn depends_on_columns (STRING, NULLABLE)>]
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                    Target columns not in source: []
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]                    New column types: []
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base] 
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base] 
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]   > in macro process_schema_changes (macros/materializations/models/incremental/on_schema_change.sql)
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]   > called by macro materialization_incremental_bigquery (macros/materializations/incremental.sql)
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]   > called by macro materialization_incremental_bigquery (macros/edr/materializations/model/incremental.sql)
[2024-03-07, 05:47:12 UTC] {pod_manager.py:395} INFO - [base]   > called by model dbt_exposures (models/edr/dbt_artifacts/dbt_exposures.sql)

Can someone advise? This happened a few more times in the past when we upgraded elementary versions so I am wondering if it’s something you need to consider when releasing new versions. I understand that breaking changes cannot be avoided, but at the same time, these kind of issues should be handled in a proper way.

Hi @George Myrianthous, Do you also upgrade the elementary dbt package + run

dbt run --select elementary

when you upgrade the CLI?

Tbf, I haven’t run

dbt run --select elementary

After upgrading the dbt package to the same minor? Are you sure you executed

dbt run --select elementary

against the same target that

edr

runs against?

No, as I mentioned I did NOT run

dbt run --select elementary

Oh sorry I was sure you said you did 😅

thanks a lot, in order to unblock our pipelines I had to drop the model which was materialised on the Data Warehouse

If you want to avoid these issues you can add a job that runs

dbt deps

+

dbt run --select elementary

will keep it in mind when a new update is out there

The build of these models is pretty lean

thanks a lot!