Closed leo-schick closed 1 year ago
@leo-schick Thanks for opening! I share your instincts about what's desirable here.
This is a quite old issue:
The good news is, we're planning to (finally) tackle that work, a few months from now, as part of a larger initiative:
In the meantime, I'm going to close this as a duplicate of #1269.
Is this a new bug in dbt-core?
Current Behavior
I have two projects:
source_ax12
which has a modelTaxTrans
.databricks_dwh
which imports projectsource_ax12
as package and has a modelTaxTrans
itself.When I parse the project, I get the error that the model
TaxTrans
exist twice.Only option I can work around myself is renaming
TaxTrans
in thedatabricks_dwh
project to something else and use a alias. But this is not something I want to do. Sub projects should not mess up my main project model naming(!) And to adjust the sub project doesn't make much sence to me. Then I mess up the model naming there. I want to have consistent, clear naming in the projects themselve.Expected Behavior
I would expect that the parsing works out and that dbt by default let the
TaxTrans
model in thedatabricks_dwh
win. It should only redirect to theTaxTrans
of thesource_ax12
project when I reference to it explicitly.Steps To Reproduce
dbt parse
Relevant log output
dbt.log
Environment
Which database adapter are you using with dbt?
spark
Additional Context
No response