Addressing the Deprecation of "DATAOWNER" and Transitioning to "TECHNICAL_OWNER"

ingestion
1

Original Slack Thread

I would like to know the current state between “DATAOWNER” and “TECHNICAL_OWNER” ownership types.
Documentation says that the “DATAOWNER” type is deprecated, and users are encouraged to use “TECHNICAL_OWNER” for technical responsibilities related to data assets, but we can still encounter many occurrences of DATAOWNER in the source code (example: <datahub/metadata-ingestion/src/datahub/ingestion/source/aws/glue.py at 25493c1f718226aeb56557c166e801c3f46c6ae3 · datahub-project/datahub · GitHub ingestion>).

What is your recommendation? Could I just provide a pull-request to re-map to TECHNICAL_OWNER when DATAOWNER is used.

It seems that the summary page “Owner Of” cannot list assets for DATAOWNER type. So, currently the ownership is set but teams or users cannot have the full list of owned data entities.

2

Hey there! :wave:

<@U06TM7M40RK> Can you help with the questions in this thread?

:information_source: Please continue to tag RunLLM (e.g <@U06TM7M40RK>) to have it continue generating responses!

3

To address your question about the “DATAOWNER” and “TECHNICAL_OWNER” ownership types, here’s a summary based on the available data sources:

  1. Deprecation of DATAOWNER: The “DATAOWNER” type is indeed deprecated. According to the <ErModelRelationship | DataHub documentation>, users are encouraged to use “TECHNICAL_OWNER” instead for technical responsibilities related to data assets. This change is part of a broader effort to streamline ownership types and make them more intuitive.

  2. Occurrences in Source Code: It’s not uncommon to find deprecated terms like “DATAOWNER” still present in the source code, such as in the <datahub/metadata-ingestion/src/datahub/ingestion/source/aws/glue.py at 25493c1f718226aeb56557c166e801c3f46c6ae3 · datahub-project/datahub · GitHub ingestion script>. This can happen due to legacy code or ongoing transitions.

  3. Recommendation: It would be beneficial to submit a pull request to re-map “DATAOWNER” to “TECHNICAL_OWNER” in the source code. This aligns with the current documentation and helps ensure consistency across the platform. Before doing so, it might be wise to check if there are any ongoing efforts or discussions regarding this transition in the project’s issue tracker or community forums.

  4. Summary Page Issue: The issue with the “Owner Of” summary page not listing assets for the “DATAOWNER” type could be due to its deprecated status. By transitioning to “TECHNICAL_OWNER,” you should be able to leverage the full functionality of the ownership features in DataHub.

Would you like more detailed guidance on how to proceed with the pull request or any other aspect of this transition?

Sources:

4

Hi :slight_smile: ! 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 :slight_smile:

Hope this helps ! ><