You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Go to 'Ingestion' tab and specify Druid configuration
Go to imported datasets and select one of them
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):
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:
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):
** Additional Context **
The text was updated successfully, but these errors were encountered: