Hi everyone! I have an issue with my glossaryTerms...
# ui
p
Hi everyone! I have an issue with my glossaryTerms. Some of them don´t appear in the UI, but if I find them by its urn (urnliglossaryTerm:Finance.Finance) they exist. Thanks😊
b
are these affected terms inside datahub already before you upgraded to a newer version with the revamped UI?
and not sure which version you upgraded to, but one of the versions require you to do a reindexing
p
Hi @better-orange-49102, thanks for your quick answer 🙂 Yes, the affected term were there before the upgrade.
We are going to check the reindexing, that could be it. Thanks!!
@better-orange-49102 We follow the indications doing the reindexing, but it doesn’t finish working
b
what does the logs say for the job
p
@better-orange-49102
Copy code
Failed to bind Urn with value urn:li:glossaryTerm:Airports).(Traffic).(Stakeholders).galeo.galeo into Urn object: java.net.URISyntaxException: mismatched paren nesting: urn:li:glossaryTerm:Airports).(Traffic).(Stakeholders).galeo.galeo
Failed Step 3/3: SendMAEStep. Failed after 0 retries.
b
asking @bulky-soccer-26729 for help 😛
p
thanks 🙂
b
sorry i cant be of more help
p
Don´t worry! You help a lot, at least we now know where is the problem 🙂
b
hey Patricia! yeah re-indexing is necessary as xL said in order for the UI to know about the hierarchy of your glossary (who the children are for the Term Group, and who the parent is for a term). It looks like you're getting an exception due to the fact that the urn has mismatching parentheses in it? is this the whole urn?
urn:li:glossaryTerm:Airports).(Traffic).(Stakeholders).galeo.galeo
?
b
This urn does indeed look malformed - it's possible this was ingested by mistake some time back
(Before we had stricter URN validation on the write apis)
p
We managed to fix it! Thanks to all 😊
🎉 1