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

Druid dataset URN is not generated correctly #11639

Open
MrdjanPoletanovic opened this issue Oct 16, 2024 · 0 comments
Open

Druid dataset URN is not generated correctly #11639

MrdjanPoletanovic opened this issue Oct 16, 2024 · 0 comments
Labels
bug Bug report

Comments

@MrdjanPoletanovic
Copy link

Describe the bug
When I sync Druid metadata, the URNs are generated using only the dataset name. For example, if the Druid dataset is named 'test-dataset', the URN is created as urn:li:dataset:(urn:li:dataPlatform:druid,test-dataset,PROD) without including a schema name before the dataset name. However, if I add the platform_instance property (e.g., marketing) in the Druid metadata spec configuration, the URN is created as urn:li:dataset:(urn:li:dataPlatform:druid,marketing.marketing.adevents,PROD), repeating the platform_instance twice.

Why is this an issue? When I try to sync Superset dashboards, Datahub cannot establish lineages between them due to the inconsistency in how the URNs are generated.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Ingestion' tab and specify Druid configuration
  2. Go to imported datasets and select one of them
  3. Look at the generated URN in browser url

Expected behavior
I believe the expected behavior is for the dataset name to be concatenated with the schema name. For example: urn:li:dataset:(urn:li:dataPlatform:druid,druid.test-dataset,PROD) if the schema name is druid, or urn:li:dataset:(urn:li:dataPlatform:druid,segments.test-dataset,PROD) if the schema name is segments.

Desktop (please complete the following information):

  • Browser : Firefox
  • Chart version: 0.14.0.2

** Additional Context **

@MrdjanPoletanovic MrdjanPoletanovic added the bug Bug report label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant