Connect Omni workbook assets to dbt model lineage#184
Merged
Conversation
Subclass OmniComponent to remap Omni query table names (e.g. BigQuery_omni_dbt_marts__fct_sessions) to dbt model asset keys (e.g. fct_sessions), enabling upstream/downstream lineage connections in the Dagster UI.
Omni Content Validator ResultsContent Validator did not produce a report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CustomOmniComponentsubclass that remaps Omni query table names (e.g.BigQuery_omni_dbt_marts__fct_sessions) to dbt model asset keys (e.g.fct_sessions)Test plan
dg list defsshows deps on Omni document assets (requires Omni env vars)