Hi all, unfortunately I am not able to add a glossary term to a schema field of a Tableau resource, e.g. a chart or dashboard, via the UI. It's only possible to assign them to the entire entity. From what I understood, https://github.com/datahub-project/datahub/pull/6119 addresses this issue, but has not made it into DataHub. Can anyone give me a status on this or have an idea for a workaround?

hey Tim! so the main reason we ended up not merging that PR is because we wanted to avoid confusion around where the source of truth is for those schemas. For Charts and Dashboards, they don't actually own their own schemas, they're just copies from some upstream dataset's schema. so if you started adding descriptions, tags, terms on the Chart, it might be confusing since you're not updating where those columns actually come from.

Well, that's a solid reasoning. Let me briefly paraphrase our use case: Currently, we only have metadata from Athena and Tableau in DataHub. We already have plans to ingrate other data sources, but have decided to focus on the two existing ones first and provide as many features as possible for them. One of our first steps is to migrate/establish our KPI glossary to/in DataHub. We don't want to link glossary terms to an entire Tableau entity because it typically contains multiple KPIs, such as reports modeled as charts in DataHub. Therefore, we rely on the ability to add glossary terms to individual schema fields of these types of entities. The above reasoning is fine as long as there is a way to automatically transfer glossary terms from upstream datasets. If that were the case, there would be no reason for us to complain 🙂 There is already a feature request for that, right?

okay gotcha! thanks so much Tim, this really helps a lot. I could definitely see other features solving this problem, like you said propagating metadata like glossary terms downstream to BI dashboard and chart schemas which is definitely a feature request. However I think it makes sense to fill out a feature request just to get this documented and see how other people feel. Would you mind creating one at this link? https://feature-requests.datahubproject.io/ honestly you could basically just copy what you have above as reasoning as I think that provides some nice context!

Alright, I'll do so Thanks for your support 🙂

of course! thanks for all your great feedback!

I would have one additional question: In case we would like to have a short term solution and modify DataHub's behavior in our fork, could we just apply the changes from the PR above or is it outdated in the mean time? 🙂

yeah I think that would be fine! there might some conflicts with more recent changes that have gone out but overall I think you should be able to take the diff from the PR and apply it to your fork.

Great, thanks a lot 🙂

awesome thank you!