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 location for Schema/Database in Unity

venkad
Contributor

Hello Bricksters,

We organize the delta lake in multiple storage accounts. One storage account per data domain and one container per database. This helps us to isolate the resources and cost on the business domain level.

Earlier, when a schema/database is created with a location, all managed tables created under that schema should be created inside the schema/database's default location.

eg:

create schema test
location ''my-test-location";
 
create table test.sample 
(col1 int);
-- it should be created in the "my-test-location/sample "

But when Unity catalog is enabled, the table gets created in the metastore's default location and schema/database's location property is ignored.

Is this an expected behavior or its a bug? If expected, when we can expect the schema location to be considered as the table's parent location?

In order to organize the data in our expected way we need to create every table with an explicit external location which is not optimal.

Thank you!

0 REPLIES 0

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now