clickzetta-external-catalog

Federated queries let you run read-only SQL across external data sources by creating storage connections, catalog connections, and external catalogs in Lakehouse. This enables cross-source analytics without migrating data from Hive, Iceberg, or Databricks.

Yes, you can query Hive and Iceberg tables by creating an external catalog in Lakehouse. This establishes a read-only federated connection, allowing you to join external tables with Lakehouse tables for cross-source analytics.

Creating an external catalog for Databricks follows a three-step workflow: create a storage connection to the data store, establish a catalog connection to a Unity Catalog-like service, and create the external catalog with read-only enforcement.

No, this approach applies read-only enforcement to external data sources. It is designed specifically to enable federated queries and cross-source analytics across Hive, Iceberg, and Databricks without allowing data modification or writes back to the external catalogs.

After establishing a catalog connection to Hive Metastore, you validate connectivity by performing sample queries across the sources. This verifies data visibility and confirms the external catalog is correctly configured for read-only federated queries.

You need a storage connection first to connect to external data stores, then a catalog connection to link to Hive Metastore or Unity Catalog-like services. Both are required prerequisites before creating an external catalog for federated queries.