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

dbt ingestion always lowercasing the table identifier urns #7853

Closed
viplazylmht opened this issue Apr 19, 2023 · 2 comments
Closed

dbt ingestion always lowercasing the table identifier urns #7853

viplazylmht opened this issue Apr 19, 2023 · 2 comments
Labels
bug Bug report stale

Comments

@viplazylmht
Copy link

Describe the bug
Follow the issue #7377, dbt ingestion always lowercasing the table identifier for urns:

When Datahub works with multiple ingestion sources, for example, dbt and bigquery, we found that because bigquery has an option convert_urns_to_lowercase default to False, the result of a table shows in datahub will be duplicated (one lowercased, other preserved).

To Reproduce
Steps to reproduce the behavior:

  1. Go to dbt project and ingest into datahub
  2. Ingest into datahub by bigquery ingestion source
  3. From datahub GUI, click on Datasets, go to the ingested table
  4. See the error (duplicated table name, one lowercased, one preserved)

Expected behavior
dbt ingestion config will have an option like convert_dataset_urns_to_lowercase, allowing users to config the case of dataset urns, seem as #7063.

Desktop (please complete the following information):

  • OS: (Ubuntu) docker quickstart
  • Browser: chrome
  • Datahub Version: 0.10.2
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

@github-actions github-actions bot added the stale label May 20, 2023
@github-actions
Copy link

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report stale
Projects
None yet
Development

No branches or pull requests

1 participant