cancel
Showing results for 
Search instead for 
Did you mean: 
Warehousing & Analytics
Engage in discussions on data warehousing, analytics, and BI solutions within the Databricks Community. Share insights, tips, and best practices for leveraging data for informed decision-making.
cancel
Showing results for 
Search instead for 
Did you mean: 

Databricks workspace default catalog not working anymore with JDBC driver

loic
Contributor

Hello,

We recently detected an issue in our product deployment with terraform.
At some point, we have some java code that creates a schema in "hive_metastore" catalog.
Since "hive_metastore" catalog is the default one, there should not be any need to specify it.
It is the implementation that has been done in the java code (catalog is not specified).

Till recently, this code was working properly.

But now, the same code complains about empty catalog.
If I explicitly set the catalog name in the java code, then the code works fine again.

The problem is that this code is in production. 
Does this new behavior is expected? Or is it a regression at some point in Databricks?

Regards,
Loïc

1 REPLY 1

loic
Contributor

The exact error reported by Databricks is:

[RequestId=f27975cd-7589-4463-8c03-6015893ee133 ErrorClass=INVALID_PARAMETER_VALUE] Invalid input: RPC CreateSchema Field managedcatalog.SchemaInfo.catalog_name: name "" is not a valid name