https://datahubproject.io logo
Join Slack
Powered by
Hi, datahub team! I was playing with the locally ...
# troubleshoot
l
Hi, datahub team! I was playing with the locally set up datahub and found an issue which I can not resolve. Starting from this week I'm not able to see the term's "custom_properties" when I go through the termName link on the web page. It just shows me the content for half of a second and then refreshes automatically to the white screen. I'm not sure why it stopped working. I've already reinstalled the datahub once again and it still shows the same behavior. Also the issue doesn't disappear when switching to another browser. May you please #troubleshoot ? Here is my testing glossary and how it looks (The first term has "custom_properties" in it):
test_glossary_terms_not_show_issue.yml
n
Same here. We went back to 0.8.39
l
It didn't help to me. @bulky-soccer-26729, or anyone from the datahub team, may you please help?
b
Same problem with v0.8.40. @big-carpet-38439 It seems to occur when the glossary term urn is not auto-generated. When trying to view a term defined in yaml and added by file ingest, a blank page is displayed.
b
hey everyone - so this issue is only occurring in 0.8.40 but not in 0.8.39? but it sounds like this issue is happening for you Larysa regardless of which of those two versions you're on? do you have any error logs to look at per chance? I believe this should be in the console as it sounds like a runtime error. I can see some of the console errors in your screenshot above but do you have the full output?
l
No, there are no logs because the ingestion is going well without any warning or error message. Also it doesn't depend on the version. I was experiencing this on 0.8.36, 0.8.39 and 0.8.40 at least.
And what I'm doing is just ingesting meta data into the datahub using the *.yml file. The terms which are created manually are good though.
n
In my case, I can confirm that the white screen is only appears for the glossary term urn is not auto-generated (which is same as Ebu's). And this problem is only appears on 0.8.40.
I'm gonna try to manually clone and run debug frontend instance for detailed error messages, and will post it here.
b
okay cool - post any updates here and I'll try to be of help! I'll also see if I can get some time today or very soon to try and reproduce myself
alright I believe I figured out the issue here! sorry for the delay
This is actually just a bug for when you ingest a business glossary via a yaml file and don't provide 
source_url
on the glossary term. I've got a fix together right now and putting up a PR as I type
that will get merged today and go out with our next release. in the meantime you can add a 
source_url
to the terms that don't have it in your yaml file and it will fix the problem! unfortunately that's kind of a hack, otherwise you can deploy off of head once this gets merged or wait until our next release. sorry about this!
👍 3
l
@bulky-soccer-26729, after datahub update to the v0.8.41 the issue is gone. Thank you!
b
great! thanks for the update
2 Views
Open in Slack
PreviousNext
Powered by