To change ownership of a materialized view

Data_NXT
New Contributor III

 working in a Unity Catalog-enabled Databricks workspace, and we have several materialized views (MVs) that were created through a Delta Live Tables (DLT) / Lakeflow pipeline.

Currently, the original owner of the pipeline has moved out of the project, and we need to transfer ownership of the materialized views to a new user/service principal.

 

  • What is the correct/supported way to transfer pipeline ownership in UC?

  • Are there any recommended steps or caveats for this process?

Thanks

 

szymon_dybczak
Esteemed Contributor III

Hi @Data_NXT ,

You can change the owner of a materialized view if you are a both a metastore admin and a workspace admin.

Use the following steps to change a materialized views owner:

  • Open the materialized view in Catalog Explorer, then on the Overview tab, click See refresh details. This opens the pipeline details for the pipeline that manages the materialized view.
  • Click Share. The Permissions Settings dialog appears. You must be a metastore and workspace admin to edit these settings.
  • Click x to the right of the current owner's name to remove the current owner.
  • Start typing to filter the list of available users. Click the user who should be the new pipeline owner.
  • Click Save to save your changes and close the dialog.

Here's a documentation:

Configure materialized views in Databricks SQL - Azure Databricks | Microsoft Learn

 

And if you would like to change owner of a pipeline as well, here's how to do this:

Cannot see how to change the owner of a DLT pipeline in the Databricks UI - Databricks

View solution in original post

i was not able to see " see refresh details " in the overview tab. I do have the Meta store admin privileges also. Does it have anything with how the pipeline has been created to see this option. Is drop/ re create  the only option in this scenario. Not able to figure it out. Any advise is appreciated. Thanks

Escarigasco
New Contributor III

Bumping, I have the same issue - @Data_NXT , were you able to solve?