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

LookML lineage to bigquery is not shown correctly due to issues in resolving variables #11893

Open
claudiovalerio5005 opened this issue Nov 19, 2024 · 0 comments
Labels
bug Bug report ingestion PR or Issue related to the ingestion of metadata

Comments

@claudiovalerio5005
Copy link

Describe the bug
We are running a looked ingestion, using datahub 14.1. Our database is bigquery. we have a problem on resolving lineage for lookml view.

the view is defiend has below:

# The name of this view in Looker is "Dm Sales Flash"
view: dm__sales_flash {
  # The sql_table_name parameter indicates the underlying database table
  # to be used for all fields in this view.
  sql_table_name: @{ric_dp_finance_sa_schema}.bqdts_controlling_copa_dm.dm__sales_flash ;;

as you can see the sql_table_name statemetn contains a variable @{ric_dp_finance_sa_schema}.

we are trying to map the variable in the lookML ingestion with setting:

    liquid_variable:
        ric_dp_finance_sa_schema: "bigquery_project_id"

Unfortunately that does not work, the lineage is not resolved.

image

In adition, i we try to assign manuallythe lineage, it will get removed the next timee the lookml ingestion runs.

@claudiovalerio5005 claudiovalerio5005 added the bug Bug report label Nov 19, 2024
@RyanHolstien RyanHolstien added the ingestion PR or Issue related to the ingestion of metadata label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Development

No branches or pull requests

2 participants