Databricks Unity Catalog Connection Issue with Multiple Schemas


I've been working with Databricks Unity Catalog as a data source in Metabase, and I encountered an issue related to schema assignment.

When connecting to the Databricks Unity Catalog, it appears that a specific schema must be assigned to the connection. Even if the user associated with the connection has access to multiple schemas within the same catalog, they are unable to visualize tables from other schemas. This limitation makes joining tables impractical, as it necessitates creating multiple connections.

Thank you in advance for your assistance!

Hi, you should contact the databricks driver developer @relferreira