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

Macro 'dbt_macro__check_schema_exists' takes no keyword argument 'information_schema' Snowflake #1492

Closed
TomRutten opened this issue Apr 16, 2024 · 3 comments
Labels
Bug Something isn't working Triage 👀

Comments

@TomRutten
Copy link

Describe the bug
Whenever I run dbt run --select elementary in my command line, Elementary will start creating the schema, tables and views in my Snowflake database. Up until the creating sql view model elementary.information_schema_columns this goes successful but the information_schema_columns fails.

To Reproduce
I followed the quickstart guide and I receive this error. I am using:

packages:
  - package: elementary-data/elementary
    version: 0.14.1

I put the following in my dbt_project.yml:

elementary:
    +schema: "elementary"

I ran dbt deps and after I ran dbt run --select elementary

Expected behavior
I expect the tables and views to be created without any issues.

Screenshots
image

Environment (please complete the following information):

  • dbt package version: 0.14.1

Additional context
None.

@TomRutten TomRutten added Bug Something isn't working Triage 👀 labels Apr 16, 2024
@haritamar
Copy link
Collaborator

Hi @TomRutten !
Thanks for opening this issue, and apologies about the delay here.
We have actually removed the information_schema_columns in Elementary 0.15 so I actually recommend upgrading to the most recent version (0.15.2).

@TomRutten
Copy link
Author

Hi @haritamar,

I am using version 0.15 but I still receive this error when doing a dbt test:
14:29:52 on-run-start failed, error: macro 'dbt_macro__check_schema_exists' takes no keyword argument 'information_schema' 14:29:52 14:29:52 on-run-end failed, error: 'None' has no attribute 'get' 14:29:52

@TomRutten
Copy link
Author

I just fixed the issue. It had to do with another macro having the same name that was in another dbt project that we imported as a package in our own dbt repo. I changed the name of this macro and it works now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage 👀
Projects
None yet
Development

No branches or pull requests

2 participants