How-to guideApplies to: Unified engine deployments
Use the native Unity Catalog provider and a saved token to read an existing
table.
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 native Unity Catalog API base URI, not its Iceberg REST URI. The API
must provide supported table-file access or the storage location must already be
accessible to Unified. Local secrets need the encrypted secret store.
Values to collect
- Native API URI, access token, remote catalog name, schema, and table.
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.
Native Unity table names contain both the remote catalog and schema after the
Unified registration name. The native provider uses credential role catalog.
The REST recipes use role auth.
Clean up
This removes only the Unified registrations. It leaves the remote catalog and
its tables in place.
Last modified on November 4, 2026
