Fix Omni-to-dbt lineage: resolve schema-prefixed asset keys#185
Merged
Fix Omni-to-dbt lineage: resolve schema-prefixed asset keys#185
Conversation
The dbt models have schema configs (e.g. schema: marts), so their asset keys are AssetKey(["marts", "fct_sessions"]), not just AssetKey(["fct_sessions"]). Load the dbt manifest to look up the correct asset key for each model name extracted from Omni table names.
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
schema: martsconfig, producing keys likeAssetKey(["marts", "fct_sessions"])— the previous approach only producedAssetKey(["fct_sessions"])which didn't matchCustomOmniComponentnow loads the dbt manifest at component load time and looks up each extracted table name to get the exact asset keyTest plan
test_custom_omni_dbt_key_lookup)