topic Unity Catalog & Delta Lake in Data Governance

Unity Catalog & Delta Lake

Tram — Mon, 14 Nov 2022 21:22:02 GMT

In setting up Databricks accounnt, we need to provide storage (s3 buckets) to store the final cleaned data or aggregated data. If the Unity Catalog is enabled at the beginning of account set up, we'd need to to provide S3 buckets again to store the metedata. My question: can it be one S3 bucket for final cleaned data and the Unity Catalog, or do they need to be separate s3 buckets?

Re: Unity Catalog & Delta Lake

Pat — Tue, 15 Nov 2022 15:27:27 GMT

HI @Tram Nguyen ,

I am not sure if I got this correctly but I believe you are referring to the:

Root storage for a workspace: Root storage for workspace objects like cluster logs, notebook revisions, and job results libraries (https://docs.databricks.com/administration-guide/account-api/aws-storage.html#configure-aws-storage)
Metastore storage: Each metastore is configured with a root storage location in an S3 bucket in your AWS account. This storage location is used for metadata and managed tables data.(https://docs.databricks.com/data-governance/unity-catalog/index.html#metastores)

It's not recommended to re-use the workspace s3 bucket for metastore.

thanks,

Pat.

Re: Unity Catalog & Delta Lake

karthik_p — Tue, 15 Nov 2022 18:22:54 GMT

@Tram Nguyen above pat provided links will have clear information. but to provide overview

account s3 bucket should be different
unity catalog s3 bucket should be different (Meta store in technical terms)

unity catalog bucket should be configured in same region of your account, so that no network Issues will be seen. multiple workspaces in that account can use same unity catalog metastore (which is s3 bucket)