Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UNRESOLVED_COLUMN exception when upgrading to elementary 0.15.1 #1538

Open
hamzamazhar opened this issue May 29, 2024 · 1 comment
Open

UNRESOLVED_COLUMN exception when upgrading to elementary 0.15.1 #1538

hamzamazhar opened this issue May 29, 2024 · 1 comment
Labels

Comments

@hamzamazhar
Copy link
Contributor

Describe the bug
When I upgrade to elementary 0.15.1 and run elementary models, it fails for the model model_run_results and throws this exception:

Runtime Error in model model_run_results (models/edr/run_results/model_run_results.sql)
  [UNRESOLVED_COLUMN.WITH_SUGGESTION] A column or function parameter with name `models`.`unique_id` cannot be resolved. Did you mean one of the following? [`run_results`.`unique_id`, `models`.`metadata_hash`, `run_results`.`query_id`, `run_results`.`name`, `run_results`.`failures`]

To Reproduce
Steps to reproduce the behavior:

  1. One a new dbt project, use elementary==0.15.0 as a package and run elementary models with dbt run -s elementary
  2. Then, upgrade the elementary package to 0.15.1 and install this package.
  3. Run the elementary models again with dbt run -s elementary and this exception occurs.

Expected behavior
Elementary models should run.

Environment (please complete the following information):

  • edr Version: 0.15.1
  • dbt package Version: 1.7.14

Additional context
Add any other context about the problem here.

@hamzamazhar hamzamazhar added Bug Something isn't working Triage 👀 labels May 29, 2024
@haritamar
Copy link
Collaborator

Hi @hamzamazhar !
Thanks for posting this issue. Unfortunately I'm not able to reproduce this, so I'm guessing this issue is a bit more specific to your environment.

I see that you are using Databricks. Are you using it with or without Unity Catalog?
Does the dbt_models table exist in the elementary schema when this error occurs?

Any additional information about your setup can help to understand this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants