How can I visualize lineage across multiple dbt projects in Dagster?

[indy-jonesy]

Hi all,

I’m working with multiple dbt projects (for example: dbt_project_A, dbt_project_B, and dbt_project_C) and want to render them together in Dagster, with lineage automatically stitched across projects. For example, some models in dbt_project_B depend on models in dbt_project_A, and dbt_project_C depends on both A and B.

What is the recommended way to load multiple dbt projects into a single Dagster repository?
How can I ensure that Dagster correctly visualizes the cross-project lineage?
Are there best practices for handling asset keys or dependencies to make this work smoothly?
Are there any example repos or documentation covering this use case?
Thanks in advance for any guidance or examples!

[santieb]

Hi

One approach that has worked for us is to explicitly define upstream assets directly in dbt sources metadata, so Dagster can stitch lineage across projects via shared asset keys.

For example, in dbt_project_B, we declare a source that points to a model materialized by dbt_project_A, and we annotate it with a Dagster asset key:

version: 2

sources:

• name: system
  database: "database"
  schema: "public"
  tables:
  • name: sales_summary
    meta:
    dagster:
    asset_key: ['warehouse', 'sales_summary']