cancel
Showing results for 
Search instead for 
Did you mean: 
Data Governance
cancel
Showing results for 
Search instead for 
Did you mean: 

External locations

Snoonan
New Contributor II

Hi all,

I am getting an error when I try to 'Browse' an external location in catalog explorer through Databricks UI.

This is the error I get:

 

Error loading files.
Input path url 'abfss://dbx-ccc-hive-metastore-unity-catalog@xxxxxxxxxx.dfs.core.windows.net/__unitystorage' overlaps with managed storage within 'ListFiles' call
 
Has anyone seen this error before and/or understands what is going wrong?
 
Thanks,
Sean
2 ACCEPTED SOLUTIONS

Accepted Solutions

NandiniN
Valued Contributor II
Valued Contributor II

Hi Sean,

This is expected for a managed path, as a user, we are not supposed to directly access paths that are managed by UC.

Hope you are able to access this KB with detailed info - https://kb.databricks.com/unity-catalog/invalid_parameter_valuelocation_overlap-overlaps-with-manage...

Thanks!

View solution in original post

Snoonan
New Contributor II

Hi @NandiniN ,

Thank you for quashing my concerns.

Thanks,

Sean

View solution in original post

5 REPLIES 5

NandiniN
Valued Contributor II
Valued Contributor II

Hi Sean,

This is expected for a managed path, as a user, we are not supposed to directly access paths that are managed by UC.

Hope you are able to access this KB with detailed info - https://kb.databricks.com/unity-catalog/invalid_parameter_valuelocation_overlap-overlaps-with-manage...

Thanks!

Snoonan
New Contributor II

Hi @NandiniN ,

Thank you for quashing my concerns.

Thanks,

Sean

gmiguel
Contributor

Adding some tips...
It seems that you have created a metastore with root path definition (metastore-level managed storage). If you're planning to deploy a multi-workspace environment (Development, QA and Production), I strongly recommend you to change this configuration to Catalog-level storage. 

Since in general those kind of environments should be isolated, you will have tough days as soon as it gets bigger when using metastore-level storage.

 

Snoonan
New Contributor II

Hi @gmiguel ,

Thank you for the advice.

Is this a setting when creating the metastore, or do I simply not specify an external location for metastore and only do so for catalogs?

Thanks,

Sean

Simply do not specify a location during metastore creation. Do it at catalog level and schema level (optional).

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.