-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
SiblingAssociationHook creates incorrect siblings for dbt entities #10406
Comments
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io |
@maiarareinaldo make sure you're following the best practices for multiple dbt projects https://datahubproject.io/docs/generated/ingestion/sources/dbt/#multiple-dbt-projects |
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: