<@U06TM7M40RK> I’m having trouble with the web UI. After ingestion the UI shows dataset and schema URIs instead of names. So instead of customer_schema I may see urn:li:container:72hdhe8847rhhdj. In the URL, I can see that the urn is actually correct (as in urn:li:dataPlatform:oracle,test,customer_schema,my table,PROD, e.g.)
It seems like you’re experiencing an issue where the DataHub UI is displaying URNs instead of the expected human-readable names for datasets and schemas. This issue can occur due to a few reasons, such as misconfiguration during ingestion or issues with the indexing in DataHub.
Based on the information from the <Slack Slack discussion>, here are a few steps you can take to troubleshoot and potentially resolve this issue:
-
Check Ingestion Configuration: Ensure that your ingestion configuration is correctly set up to include the necessary metadata aspects. This includes ensuring that the schema and dataset names are correctly specified in your ingestion recipe.
-
Reindexing: Sometimes, the issue might be due to a desynchronization between the metadata stored in the backend (e.g., MySQL) and the search index (e.g., Elasticsearch). Reindexing the data can help resolve this. You can use the <https://datahubproject.io/docs/api/restli/restore-indices/|restore indices> API to reindex your data.
-
Check Browse Paths: Ensure that the browse paths are correctly set for your datasets. Incorrect or missing browse paths can lead to issues with how datasets are displayed in the UI. You can customize browse paths using the DataHub Python client, as shown in the <Slack Slack discussion>.
-
Platform Instances: If you are using platform instances, ensure they are correctly configured. This can help in organizing and displaying datasets correctly in the UI. More information on platform instances can be found https://datahubproject.io/docs/platform-instances/|here.
Would you like more detailed steps on any of these troubleshooting methods?
Sources:
0 button 
0 button 
Hint: Mention