<@U06TM7M40RK> when using meta_mapping
data_tier:
match: “Bronze|Silver|Gold”
operation: “add_term”
config:
term: “{{ $match }}”
it’s creating a new glossary term rather than using the existing one.
How can I map the URN?
<@U06TM7M40RK> when using meta_mapping
data_tier:
match: “Bronze|Silver|Gold”
operation: “add_term”
config:
term: “{{ $match }}”
it’s creating a new glossary term rather than using the existing one.
How can I map the URN?
To map the URN of existing glossary terms instead of creating new ones, you need to ensure that the term
configuration in your meta_mapping
section correctly references the URNs of the existing glossary terms. The issue you’re facing is likely because the term
configuration is using the matched string directly, which results in the creation of new terms if they don’t match existing URNs.
According to the <https://datahubproject.io/docs/0.14.0/generated/ingestion/sources/dbt#dbt-meta-automated-mappings|DataHub documentation on dbt meta mapping>, you can specify the exact URNs of the glossary terms you want to map. Here’s how you can modify your configuration:
meta_mapping:
data_tier:
match: "Bronze|Silver|Gold"
operation: "add_term"
config:
term: "urn:li:glossaryTerm:{{ $match }}"
In this configuration, replace urn:li:glossaryTerm:{{ $match }}
with the actual URNs of your existing glossary terms. For example, if the URN for “Bronze” is urn:li:glossaryTerm:bronze-urn
, you should specify it directly:
meta_mapping:
data_tier:
match: "Bronze"
operation: "add_term"
config:
term: "urn:li:glossaryTerm:bronze-urn"
Repeat this for each term (“Silver”, “Gold”) with their respective URNs.
Would you like more detailed steps or additional examples on how to address this issue?
Sources:
<@U06TM7M40RK> can you share the code with silver and gold
Certainly! To map existing glossary terms for “Silver” and “Gold” using their URNs, you need to specify each term’s URN in the meta_mapping
configuration. Here’s an example of how you can set this up:
meta_mapping:
data_tier:
match: "Bronze|Silver|Gold"
operation: "add_term"
config:
term: "{{ $match }}"
To use specific URNs for “Silver” and “Gold”, you would modify the configuration like this:
meta_mapping:
data_tier:
match: "Bronze"
operation: "add_term"
config:
term: "urn:li:glossaryTerm:bronze-urn"
data_tier:
match: "Silver"
operation: "add_term"
config:
term: "urn:li:glossaryTerm:silver-urn"
data_tier:
match: "Gold"
operation: "add_term"
config:
term: "urn:li:glossaryTerm:gold-urn"
In this configuration, replace urn:li:glossaryTerm:bronze-urn
, urn:li:glossaryTerm:silver-urn
, and urn:li:glossaryTerm:gold-urn
with the actual URNs of your existing glossary terms for “Bronze”, “Silver”, and “Gold”.
This setup ensures that the existing glossary terms are used instead of creating new ones.
Would you like more detailed steps or additional examples on how to address this issue?
Sources:
Hi ! Did this interaction resolve your issue or do you still require assistance ?
Please tag @ RunLLM if you still need further assistance !
Or tag @Datahub Community Support if you require a person to take a look
Hope this helps ! ><