fix(ingestion): Looker original view name should be used for explore_joins #4928
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.
Looker Explore consists of Looker Views.
For example,
revenue
explore's base view isopportunity
and it joins withfeature_enablement
. Here,feature_enablement
is just the name of the join and its original view name isapp_subscription
.Current issue of the Looker ingestion in the case of
join
hasfrom
attribute is the upstream metadata of the explore (e.g;revenue
explore) does not use the original view name (e.g;app_subscription
) but use the join name (e.g;feature_enablement
). Join name dataset entity is just empty.In this PR, I made a fix for the above issue.
Checklist