From 8daebe6e580f3b96924612a54d910c5e9aa42032 Mon Sep 17 00:00:00 2001 From: Jason Ganz Date: Tue, 13 Feb 2024 12:24:11 -0500 Subject: [PATCH] tweak formatting --- website/blog/2024-02-13-dbt-explorer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/2024-02-13-dbt-explorer.md b/website/blog/2024-02-13-dbt-explorer.md index cb78ae99c81..9dbc1b7db7c 100644 --- a/website/blog/2024-02-13-dbt-explorer.md +++ b/website/blog/2024-02-13-dbt-explorer.md @@ -43,7 +43,7 @@ dbt Explorer builds on this experience in three key ways: - **Cross project lineage -** if you’re using the new [dbt Mesh](https://www.getdbt.com/product/dbt-mesh) architecture, you may trace your data back to the end of the DAG and find its source is not raw data, but in fact the output of another team’s dbt project! Luckily, dbt Explorer provides first class support for visualizing and understanding cross project lineage when using the dbt Mesh: - **Account View + Project DAG:** dbt Explorer provides a higher level view of the relationships between all your projects in your dbt Cloud Account — you can trace the lineage across the projects, and easily drill down into each project. When you click on a project in this view, the side panel includes a list of all the public models available for use. Double clicking opens up the lineage for that specific project, making it easy to traverse across your organization’s knowledge graph! - **Cross Project Icons:** When you’re in a project’s lineage, dbt Explorer marks cross-project relationships to make it clear when there are dependencies that span multiple projects. Stakeholders can quickly understand which project owners they may need to contact if they need more information about a dataset. -- **Column level lineage -** long time [listeners of the pod](https://github.com/dbt-labs/dbt-core/discussions/4458) know that column level lineage is a frequently requested feature within dbt. It’s one thing to know how data flows between models, but the column level relationships help you understand *precisely* how data is used in models — this makes debugging data issues a lot simpler! We’re stoked to announce that dbt Explorer offers this feature embedded alongside your model lineage as well. +- **Column level lineage -** long time listeners of the pod know that column level lineage is a frequently requested feature within dbt. It’s one thing to know how data flows between models, but the column level relationships help you understand *precisely* how data is used in models — this makes debugging data issues a lot simpler! We’re stoked to announce that dbt Explorer offers this feature embedded alongside your model lineage as well.