You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
dbt ingestion creates wrong siblings for dbt models that are also defined as sources in the dbt project. Like in the picture, there were suppose to be only l4b_flags Athena and dbt entities in the Composed Of section, instead there are 2 extra dbt models that shouldn't be there. (Note: the 2 extra models are downstream to the l4b_flags one.)
To Reproduce
Steps to reproduce the behavior (a prerequisite is to have a dbt model that is also defined as a source in the dbt project):
Have separate recipes: one to ingest dbt sources only and the other to ingest models only (instead of having a single recipe to ingest the both, this is needed to ensure the models keep their upstream lineage).
Run the sources recipe ingestion
Run the models recipe ingestion
Run the sources recipe ingestion a second time (this is when the bug is introduced).
Expected behavior
The dbt siblings are created correctly.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: iOS
Browser: chrome
The text was updated successfully, but these errors were encountered:
Describe the bug
dbt ingestion creates wrong siblings for dbt models that are also defined as sources in the dbt project. Like in the picture, there were suppose to be only
l4b_flags
Athena and dbt entities in theComposed Of
section, instead there are 2 extra dbt models that shouldn't be there. (Note: the 2 extra models are downstream to thel4b_flags
one.)To Reproduce
Steps to reproduce the behavior (a prerequisite is to have a dbt model that is also defined as a source in the dbt project):
Expected behavior
The dbt siblings are created correctly.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: