cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Using AD groups for object ownership

dpc
Contributor

Databricks has a general issue with object ownership in that only the creator can delete them.

So, if I create a catalog, table, view, schema etc. I am the only person who can delete it.

No good if it's a general table or view and some other developer wants to delete it.

Or if you create it within a notebook and want to test that the notebook works e.g. a notebook that creates or replaces a view that you change. SO, what do you do if another dev needs to work on it

Also, what happens if the individual leaves after historically creating a number of tables that the own.

 

Some time ago I asked the question and was told that databricks was looking at AD group ownership (or some other form of grouped ownership) i.e. the groups owns the object, so if you are in that group you have the same ownership rights rights.

 

Is that still in progress as I cannot find anything further.

Either I am missing a point or the whole ownership area is still not very good.

 

Thanks

 

 

0 REPLIES 0