User16871418122
Databricks Employee
Databricks Employee

hi @Arif Ali​  You may have to check the data access config to add the params for external metastore:

spark.hadoop.javax.jdo.option.ConnectionDriverName org.mariadb.jdbc.Driver

spark.hadoop.javax.jdo.option.ConnectionUserName <mysql-username>

spark.hadoop.javax.jdo.option.ConnectionPassword <mysql-password>

spark.sql.hive.metastore.version <hive-version>

spark.sql.hive.metastore.jars <hive-jar-source>

Screenshot 2021-11-17 at 8.24.33 AM 

If the data access config is already added, it is likely the metastore initialization is taking longer. ie( spark to apply the spark configs to load metastore). If given some more time it will initialize the metastore and enables schema browsing. If still issues, the configs may be wrong, you shall have them validated on interactive Databricks cluster before applying in SQL endpoints.

In the near future with the Unity catalog, the schema browsing is cluster less. The dependency on having a cluster is removed. 😊

View solution in original post