-
Notifications
You must be signed in to change notification settings - Fork 100
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
Snapshot - macro 'dbt_macro__create_schema' takes not more than 1 argument(s) #208
Comments
I found a work-around. If I delete the certain lines below from what I think comes from the dependency install of dbt-core, I am able to run snapshot successfully. Perhaps this is a dbt-core issue? |
Hi! It looks more like configuration or authorisation problem. Can you run any model? The failing part is when dbt tries to create the schema that does not exist. Do you have any special chars in the schema name? |
Hi @mikaelene, I have two snapshot and both run into the 'dbt_macro__create_schema' issue above. I can run a model-paths model successfully without error. To expand a little more on the above work-around, when I go into the python environment then Lib/site-packages/dbt/include/global_project/macros/materializations/snapshots/snapshots.sql and delete lines 9-11, the adapter.check_schema_exists section, then the snapshot compile and execute without issue. |
Hi, Did you specify target_schema somewhere? /Mikael |
I had target_schema specified in the dbt_project.yml. Using the work-around I mentioned above, the snapshots did land in the schema specified on the dbt_project.yml. I just tried adding the target_schema specification into the config of the snapshot model and resulted in the same error. |
Hi @mikaelene, Indeed this appears to be a dbt-core issue. @jtcohen6 has researched that above lines in dbt-core are unnecessary and will be removed via dbt-labs/dbt-core#4993 |
Hi trying out snapshots on SQL Server 2017 and I'm running into an odd issues that I can't make out what is going on. Apologies if this is stackoverflow territory, but this seems simple enough that there might be a bug. I have a fresh virtual environment with the packages listed below at the end.
Using this table as my test (models\test.sql)
and then trying this snapshot (snapshots\test.sql}
I get this error:
full log:
pip freeze:
The text was updated successfully, but these errors were encountered: