โ08-29-2022 01:45 AM
Now that Unity Catalog is GA, I was wondering how y'all implemented it (or planning to do so) on a workspace level.
Do you create a separate 'one workspace to rule them all' with the Unity Catalog, or do you create it on an already existing workspace (PRD f.e.)?
โ08-29-2022 05:06 AM
I didn't think about it before, but it sounds interesting to have another workspace with limited access to do the administration work.
In my case I will go rather with the DEV/TEST (ws) -> PROD (ws) that we use only to develop and execute ETL pipelines.
โ08-29-2022 01:51 AM
Hello @Werner Stinckensโ Can you please refer to the below doc for UC
https://docs.databricks.com/data-governance/unity-catalog/get-started.html
โ08-29-2022 01:54 AM
I believe it will depend on the use case.
โ08-29-2022 04:53 AM
Are you thinking about creating totally separate workspace just to manage Unity Catalog?
I've been playing a bit with the Unity Catalog and I am currently thinking about managing it from one of the existing workspaces. I don't think there is need for separate one, unless you have some spare once.
I am thinking about DEV and PROD Unit Catalogs and DEV one will be managed from the existing DEV workspace and PROD from the existing PROD workspace.
On one hand it sounds tempting if I got you correctly - similar to having the AWS account just for CI/CD.
โ08-29-2022 04:55 AM
Well that is one of the options. I know it is not a technical requirement but it could be interesting.
On the other hand: We already have a workspace so why create another one...
Hence my question ๐
โ08-29-2022 05:06 AM
I didn't think about it before, but it sounds interesting to have another workspace with limited access to do the administration work.
In my case I will go rather with the DEV/TEST (ws) -> PROD (ws) that we use only to develop and execute ETL pipelines.
โ12-24-2022 07:17 PM
@Pat Sienkiewiczโ There can be only 1 Unity Catalog metastore per azure region and if your DEV and PROD are in one region then it means all our dev and prod catalogs will be in single metastore. This also means as long as you have admin permission on databricks account and metastore , you can login to any dev or prod workspace to manage the metasore content (such as storage credentials, external locations, catalogs / schemas , grp/user permissions etc ).
@Prabakar Ammeappinโ and @Abishek Subramanianโ I wish the databricks account admin console UI had features to manage storage credentials, external locations, catalogs / schemas , grp/user permissions so that we don't have to perform metastore admin tasks from a workspace UI.
Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโt want to miss the chance to attend and share knowledge.
If there isnโt a group near you, start one and help create a community that brings people together.
Request a New Group