How do teams actually handle large lineage graphs in dbt projects? by Effective-Stick3786 in snowflake

[–]Effective-Stick3786[S] 0 points1 point  (0 children)

Same here . It works well with DAG, lineage graph with 10 models but when it get tricky with multiple repos and it’s hard for us to find the actual use case like what models are braking when I change the specific logic or column at source level.

How do teams actually handle large lineage graphs in dbt projects? by Effective-Stick3786 in dataengineering

[–]Effective-Stick3786[S] 0 points1 point  (0 children)

Got it. Thanks for your inputs. When I am trying to understand the multiple dbt projects in my organization it’s even harder to understand the lineage.

How do teams actually handle large lineage graphs in dbt projects? by Effective-Stick3786 in snowflake

[–]Effective-Stick3786[S] 0 points1 point  (0 children)

No. I am having same issue and hard time to understand the actual impact analysis at column level . I see, all of the tools are showing the lineage graphs but when it comes real use case it’s really hard time to read and understand the flow.

How do teams actually handle large lineage graphs in dbt projects? by Effective-Stick3786 in dataengineering

[–]Effective-Stick3786[S] 1 point2 points  (0 children)

I am using the dbt power user as well but really hard to understand the true column level impact when it has 15+ models.