Skip to main content

Why doesn’t an indirectly referenced upstream public model appear in Explorer?

For project dependencies in Mesh, Catalog only displays directly referenced public models from upstream projects, even if an upstream model indirectly depends on another public model.

So for example, if:

  • project_b adds project_a as a dependency
  • project_b's model downstream_c references project_a.upstream_b
  • project_a.upstream_b references another public model, project_a.upstream_a

Then:

  • In Explorer, only directly referenced public models (upstream_b in this case) appear.
  • In the Studio IDE lineage view, however, upstream_a (the indirect dependency) will appear because dbt dynamically resolves the full dependency graph.

This behavior makes sure that Catalog only shows the immediate dependencies available to that specific project.

Was this page helpful?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

0