fix(ingest): Fix postgres lineage within views #8906
Merged
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.
include_view_lineage
is set toTrue
andplatform_instance
is set to a value in a Postgres ingestion recipe, the lineage within views doesn't work.make_dataset_urn
function is used instead ofmake_dataset_urn_with_platform_instance
in the lineage resolving function. Themake_dataset_urn
function cannot resolve the upstream tables since it doesn't accept theplatform_instance
parameter.make_dataset_urn_with_platform_instance
function instead ofmake_dataset_urn
, ensuring that the lineage always works, whether or not aplatform_instance
value is present.Checklist