topic Re: AssertionError Failed to create the catalog in Machine Learning

AssertionError Failed to create the catalog

Lcsp — Thu, 11 Apr 2024 23:06:35 GMT

getting this error when trying to setup the get-started-with-databricks-for-machine-learning LAB . Unity catalog is enabled.

Validating the locally installed datasets: | listing local files...(0 seconds) | validation completed...(0 seconds total) Creating & using the catalog "........._da"

AssertionError: Failed to create the catalog "...._da". Please see the "Troubleshooting | Cannot Create Catalog" section of the "Version Info" notebook for more information.

Re: AssertionError Failed to create the catalog

PL_db — Mon, 22 Apr 2024 09:06:53 GMT

It looks like you don't have the CREATE CATALOG privilege on the metastore you're trying to create the catalog in:

Privilege types by securable object in Unity Catalog

Re: AssertionError Failed to create the catalog

SalP — Mon, 27 May 2024 22:10:11 GMT

Did you ever get this solved? I'm seeing the same issue.

Re: AssertionError Failed to create the catalog

SalP — Mon, 27 May 2024 22:17:03 GMT

In particular: the error message refers to a troubleshooting notebook, which in turn refers out to a document https://files.training.databricks.com/static/troubleshooting.html#cannot-create-catalog, which at this moment just says "Coming Soon". ????

Re: AssertionError Failed to create the catalog

SalP — Mon, 27 May 2024 23:47:33 GMT

EDIT: I found the issue in my Databricks metastore was that it did not have a default storage location set. The academy setup scripts don't explicitly set MANAGED LOCATION and therefore without a default location it fails.

I tried to establish a default storage location on my existing metastore but it didn't work for some reason - silently failed, not sure where to look for logs or error messages. But, I confirmed this was the issue because I set up a new metastore (in a different region) and a new workspace, and at metastore creation time I set a default S3 bucket, and then - voila - CREATE CATALOG worked fine without specifying managed location.