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: 

Default catalog created wrong on my workspace

amarnadh-gadde
New Contributor II
We have provisioned a new databricks account and workspace on premium plan. When built out workspace using terraform, we expected to see a default catalog matching workspace name as per this documentation. However I dont see it. All I see are the 3 catalogs below and the default catalog for the workspace is pointed to the legacy hive_metastore. Can you help how to fix this. 
 
5 REPLIES 5

NandiniN
Databricks Employee
Databricks Employee

I am also able to see just these 3, I think it is meant to be "My organization"

@NandiniN My organization is a grouping not a catalog. When I run SHOW CATALOGS I get below, which tells me it could be probably "system", but that is not setup as default right now. The terraform documentation I link I provided above says we should have a catalog created by default matching workspace name. 

amarnadhgadde_0-1738349830739.png

 

saurabh18cs
Valued Contributor III

The legacy Hive metastore is maintained for backward compatibility.  When you start using Unity Catalog compatible compute i.e. when the workspace has an assigned Unity Catalog metastore, and the cluster is in access mode 'Shared' or 'Single User', or in SQL warehouses then you to reference a fully qualified 3 level name. Catalog.Schema.table.

Run the following SQL queries to check if Unity Catalog is enabled and to list the catalogs and schemas.

-- List catalogs
SHOW CATALOGS;
-- List schemas in a specific catalog
SHOW SCHEMAS IN <catalog_name>;

amarnadh-gadde
New Contributor II

@saurabh18cs Ours is a new account and as I represented in the screenshots above, for new accounts databricks documents suggests we will have a new catalog created matching workspace name. However that never happened in our account and the default catalog for our workspace points to the hive_metastore catalog. I do not want to use hive_metastore catalog. I am working towards creating my own catalog for the workspace and attach it to the UN=nity metastore, but I expected a new catalog be already there as per their documentation. 

@amarnadh-gadde let me explain you again to make it more clear.

1) My orgaisation will act as your unity catalog catalog.

2) Ignore what is showing default there and ignore hive_metastore

3) start using unity catalog via uc enabled compute and 3 level namespace (catalog.schema.table)

Just try using it , I believe everything is correct at your side.

Connect with Databricks Users in Your Area

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