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

BI Lineage (Looker) not detecting usage in derived tables #1763

Open
PatFitzner opened this issue Dec 16, 2024 · 0 comments
Open

BI Lineage (Looker) not detecting usage in derived tables #1763

PatFitzner opened this issue Dec 16, 2024 · 0 comments
Labels
Bug Something isn't working Triage 👀

Comments

@PatFitzner
Copy link

PatFitzner commented Dec 16, 2024

Describe the bug
Hello!

We have connected our instance of Elementary Cloud to Looker in order to enable Lineage to Downstream Dashboards and Tools. When a table from our DWH is referenced in a Looker view definition, the corresponding exposure is successfully generated and visible in our lineage.

view: view_name {
  sql_table_name: `project.dataset.table`
    ;;

However, when the DWH table is referenced within the definition of a derived table, no exposure is created in our lineage.

view: view_name {
  derived_table: {
    sql:
      SELECT * FROM `project.dataset.table`  ;;
  }

Environment (please complete the following information):

  • Elementary dbt package version: 0.16.1
  • dbt version you're using: cloud (versionless)
  • Data warehouse: BigQuery
@PatFitzner PatFitzner added Bug Something isn't working Triage 👀 labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage 👀
Projects
None yet
Development

No branches or pull requests

1 participant