Skip to content

[ingestion/dbt] New UI can not present columns to us after ingesting dbt file to datahub #13249

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

Closed
Comet-Co opened this issue Apr 17, 2025 · 2 comments
Assignees
Labels
bug Bug report datahub-v1.0-rc Issue or PR related to DataHub v1.0 Release Candidates

Comments

@Comet-Co
Copy link

Describe the bug

  1. New UI can not present columns to us after ingesting dbt file to datahub. dbt files attached as follows.
  2. Each Node name in Lineage attached database name.
    dbt model file content is as follows:
    {{ config(materialized='table'
    ) }}
    select urn, aspect, version, metadata, systemmetadata, createdon, createdby, createdfor
    from {{ source('dwd','metadata_aspect_v2') }}
    source.yml content is as follows:
    version: 2
    sources:
    • name: dwd #模型中引用的名称
      schema: public #实际数据库名
      tables:
      - name: metadata_aspect_v2

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
Every node in Lineage page could present columns in new UI.

Screenshots and/or Screen Recordings

Image

System details (please complete the following information):

  • DataHub Version Tag [e.g. v1.0-rc1]
  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

@Comet-Co Comet-Co added bug Bug report datahub-v1.0-rc Issue or PR related to DataHub v1.0 Release Candidates labels Apr 17, 2025
@NoamMosko
Copy link

I've been using CLI version 0.15.0.5 with DBT, and it has worked well. However, after upgrading to version 1.0.0.2, I’ve noticed a few significant issues:
Missing Raw and Formatted SQL: Previously, I was able to view both the raw and formatted SQL. After the upgrade, I only see the view definition. I've attached a screenshot for reference.
Column Lineage Not Working: This is the most critical issue—column lineage is no longer displaying correctly. The lineage information appears to be missing or inaccurately presented.

is it related to this?

@Comet-Co
Copy link
Author

I've been using CLI version 0.15.0.5 with DBT, and it has worked well. However, after upgrading to version 1.0.0.2, I’ve noticed a few significant issues: Missing Raw and Formatted SQL: Previously, I was able to view both the raw and formatted SQL. After the upgrade, I only see the view definition. I've attached a screenshot for reference. Column Lineage Not Working: This is the most critical issue—column lineage is no longer displaying correctly. The lineage information appears to be missing or inaccurately presented.

is it related to this?

Yes,the issue is related. I was wondering upgrade the datahub version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report datahub-v1.0-rc Issue or PR related to DataHub v1.0 Release Candidates
Projects
None yet
Development

No branches or pull requests

5 participants