Adding config to have dbt-databricks add catalog and schema information to the path of external tables, to reduce the likelihood of conflicts arising from tables with the same name. This is a huge pain in testing, but not sure if others hit this in the wild, hence why default is to not do this behavior. We probably should have always been doing this, but it could potentially break existing workflows, another reason to default to False.
Checklist
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.
Resolves #812
Description
Adding config to have dbt-databricks add catalog and schema information to the path of external tables, to reduce the likelihood of conflicts arising from tables with the same name. This is a huge pain in testing, but not sure if others hit this in the wild, hence why default is to not do this behavior. We probably should have always been doing this, but it could potentially break existing workflows, another reason to default to False.
Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.