How-to guideApplies to: Unified engine deployments
Register Unity Catalog Iceberg REST in Unified and read an existing table with
OAuth client credentials.
Before you start
Use an existing catalog with at least one readable Iceberg table. The engine and
workers must reach the catalog and its table storage. Have the remote identity
and permissions ready before creating the Unified registration. Replace the
namespace and table with one you know has data.
Use the Iceberg REST endpoint supplied by your workspace administrator. It
differs from the native Unity Catalog API. The selected table must be exposed
through that REST interface.
The service must return usable temporary storage credentials, or the table
location must already have configured storage access in Unified. Requesting
delegation alone does not grant access. Local secret values require the
encrypted secret store.
Values to collect
- Catalog API URI, warehouse, namespace, and table.
- Client ID, client secret, and token endpoint. Confirm that the application can request the all-apis scope.
Run the SQL
Replace every <placeholder> before running. Use unused names for the resources
below. Run the statements in order in Workbench.
Check the result
The SELECT should return up to five rows from the chosen table. Use a nonempty
table for this check. This verifies both metadata and table-file access;
creating the registration alone does not verify either.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
Last modified on November 4, 2026
