Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update ide image #4066

Merged
merged 4 commits into from
Sep 12, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/terms/data-lineage.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ In the greater data world, you may often hear of data lineage systems based on t

If you use a transformation tool such as dbt that automatically infers relationships between data sources and models, a DAG automatically populates to show you the lineage that exists for your [data transformations](https://www.getdbt.com/analytics-engineering/transformation/).

<Lightbox src="/img/docs/terms/data-lineage/dag_example.png" title="dbt Cloud Project with generated DAG" />
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
<Lightbox src="/img/docs/terms/data-lineage/dag_example.jpg" width="80%" title="dbt Cloud Project with generated DAG" />

Your <Term id="dag" /> is used to visually show upstream dependencies, the nodes that must come before a current model, and downstream relationships, the work that is impacted by the current model. DAGs are also directional—they show a defined flow of movement and form non-cyclical loops.

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading