Hello all! I'm running into an issue with the lat...
# community-support
r
Hello all! I'm running into an issue with the latest version of Elementary and not getting a report generated. I did do
dbt deps
as well as install the latest CLI with pip install, and after that did a
dbt run --target staging --select elementary
which ran without issue. Is there anything further I can do to get this resolved?
Copy code
2024-01-12 19:43:54 — INFO — Running with edr=0.13.2
2024-01-12 19:44:04 — INFO — edr (0.13.2) and Elementary's dbt package (0.13.2) are compatible.
2024-01-12 19:44:30 — INFO — Running dbt --log-format json run-operation elementary.log_macro_results --args {"macro_name": "elementary_cli.get_exposures", "macro_args": {}} --project-dir /usr/local/lib/python3.12/site-packages/elementary/monitor/dbt_project --profiles-dir . --target staging
2024-01-12 19:44:36 — ERROR — Could not generate the report - Error: Failed to run dbt command.
INFO - BigQuery adapter: <https://console.cloud.google.com/bigquery?project=REDACTED&page=queryresults>
INFO - Encountered an error while running operation: Database Error
INFO -   Queries in UNION DISTINCT have mismatched column count; query 1 has 20 columns, query 2 has 19 columns; failed to parse view 'REDACTEDPRJID.dbt_transform_monitor.enriched_exposures' at [13:2]
INFO - Please reach out to our community for help with this issue.[
INFO - NoneType: None
Although the easiest way to repro is just: `
Copy code
select * from dbt_transform_monitor.enriched_exposures limit 1;
(we use dbt_transform_monitor as our schema for elementary / dbt_transform is the output schema for dbt run) dbt_exposures table has 20 columns and elementary_exposures has 19, so the union distinct is unhappy.
✅ 1
e
Hi @Renee Cooper, care to drop the
enriched_exposures
view? We've made some changes that don't require this table for generating a report. Dropping the view should fix the issue, apologies for the inconvenience.
thankyou 1
👀 2
r
Thanks Elon, that did work.
🙌 2
c
@Elon Gliksberg we got this error now upgrading to 0.14.1, how can it not have been resolved yet?
Is it due to the fact that dbt does not remove models?