Issues Creating External Tables in Hive Metastore vs. Unity Catalog

Data Governance

Join discussions on data governance practices, compliance, and security within the Databricks Community. Exchange strategies and insights to ensure data integrity and regulatory compliance.

Hi Databricks Community,

I’m encountering some challenges when working with external tables in Databricks. I’m using both Unity Catalog and Hive Meta store and have noticed differences in how external tables are handled.

Unity Catalog: I can successfully create a Delta table using the following query, specifying an external location:

CREATE TABLE IF NOT EXISTS 'UC-catalog.schema.table'
USING DELTA
LOCATION 'Path'.

2.Hive Metastore: When I attempt a similar approach using the Hive Metastore, I run into problems. The table gets created, but I am unable to see the data. Here is the query I used:

CREATE TABLE IF NOT EXISTS 'hivemetastore.schema.table'
USING DELTA
LOCATION 'Path'.

Despite the table being created, the data isn’t visible. And facing below error

Questions:

Can external tables be created in Hive Metastore from external locations like Azure Blob or AWS S3 buckets? If so, what is the correct approach?
What could be causing the data visibility issue in Hive Metastore? I’ve checked the path and permissions but am still encountering problems.

Any guidance or best practices for handling external tables in Hive Metastore would be greatly appreciated!

Thanks in advance for your help!