This message was deleted.

Thanks for reporting @best-window-95315 , it’s likely a bug on our end but let me double check this morning and I'll let you know what we find.

We're not able to see our dbt source tables in the lineage, any reason why? We can only see lineage between dbt models.

Interesting that is still happening for you. In our dbt integration we were originally just extracting

model

node types from the

manifest.json

. Then in the changes we pushed above, we removed that constraint to pull in the other node types, which lead to the issue you experienced earlier this week with tests being pulled in. Now we’ve limited the extraction to pull in

model

and

seed

types from the manifest.json. Do you know @blue-ocean-91219 if in your

manifest.json

you have the source tables as

seed

nodes? If so they should be pulled into Secoda lineage.

Okay that makes sense. We are seeing

seed

nodes but we'd also like to eventually see connections to

source

nodes. These source tables are being pulled in by our snowflake integration but can't see lineage to downstream

model

nodes.

Ah that makes sense @blue-ocean-91219. @lively-helicopter-98030 has been working this week on improving lineage through SQL parsing Snowflake queries, so it’ll be good to see if those changes are able to resolve this issue.

Okay great! But also, these

source

nodes are defined in the

manifest.json

file too

Oh okay, I’ll update the integration to also accept

source

nodes. That’s a quick fix

Awesome, let me know!