Hey Team, I found one issue while I was trying to ...
# ingestion
r
Hey Team, I found one issue while I was trying to understand how to ingest existing metadata to datahub. In the current code, it automatically use "li" as all Urn domain. Maybe we need to have a configurable way to set the urn domain? example: a user entity might have urn as "urn:*li*corpUserfoo"
b
Hi @red-napkin-59945 - Totally hear you on the urn namespace issue. For the "next generation" of urns, we will be using the "dh" namespaces to represent DataHub. Unfortunately, customizing this would be quite challenging today mainly due to the ingestion sources that depend on it!
cc @orange-night-91387 Who has been thinking about this reently
👀 1
o
We're still ironing out some of the designs, but we definitely want to have more flexibility around namespacing. The current codebase has some baked in assumptions around the li namespace and without some reworking a different namespace will not work. Making urns less of a pain point is a big priority for us 🙂
r
thankyou1