Hey all! Since 0.8.16, ingesting a dbt model will create two nodes - one for the dbt model and one for the underlying platform. I think this is definitely an improvement over the previous behavior, but it does seem to make lineage a bit more complex because all chains are now double the length 🙂 Is there a way around this? Ideally I think we'd see eg. a merged dbt/bigquery node in the lineage graphs, that would combine the information.

try

disable_dbt_node_creation

flag in recipe

Unfortunately, with that option it doesn't look like all information is being ingested from dbt. We also like the discoverability of having the dbt nodes as their own platform. So I was wondering whether there was a way to have the best of both worlds ^^

@quaint-branch-37931: thanks for the feedback. We're thinking about this 🙂 /cc @green-football-43791

Let me know if I can help in any way! I feel like there is a similar situation with AWS Athena (https://datahubspace.slack.com/archives/CUMUWQU66/p1641978224103100?thread_ts=1641819373.060700&cid=CUMUWQU66). I'd imagine there must be more!

We are seeing something similar with an in house platform we run similar to DBT - would be great to somehow make this generic

@quaint-branch-37931: would you mind filing a feature request for this?