167 added a create schema if not exists clause, but only defines the schema and not the database. If your external table is sourced out of a different database than your dbt profile, this causes an empty schema to be created in your dbt profile database.
Steps to reproduce
Define an external table with a database != dbt profile database. In our case, these are raw and analytics, respectively.
Expected results
Creating the schema in the source database
Actual results
Creating the schema in the dbt profile database
Screenshots and log output
System information
The contents of your packages.yml file:
Which database are you using dbt with?
[ ] redshift
[x] snowflake
[ ] other (specify: ____)
The output of dbt --version:
1.3.0
The operating system you're using:
Ventura 13.3.1
The output of python --version:
Describe the bug
167 added a
create schema if not existsclause, but only defines the schema and not the database. If your external table is sourced out of a different database than your dbt profile, this causes an empty schema to be created in your dbt profile database.Steps to reproduce
Define an external table with a database != dbt profile database. In our case, these are
rawandanalytics, respectively.Expected results
Creating the schema in the source database
Actual results
Creating the schema in the dbt profile database
Screenshots and log output
System information
The contents of your
packages.ymlfile:Which database are you using dbt with?
The output of
dbt --version:The operating system you're using: Ventura 13.3.1 The output of
python --version:Additional context