Before you can read and write Unity Catalog tables, you need to connect Wherobots to Databricks Unity Catalog.
Before you start
- A Databricks workspace with Unity Catalog enabled and a catalog created.
- A Wherobots account with access to your Iceberg or Delta Table in Databricks Unity Catalog.
- In order to read and write Unity Catalog tables, ensure that your Databricks workspace is configured correctly by completing the steps in Connect to Databricks Unity Catalog.
Set the SedonaContext
In a Wherobots Notebook, create theSedonaContext and import any other necessary libraries for your analysis.
The following imports the necessary modules from the Sedona library, creates a SedonaContext object, and
imports expr.
Set your Databricks Resource Variables
Define the resources that point to your Databricks resources:Reading from a Delta Table
- Writing to a Wherobots-managed catalog
- Writing to an External Delta Table in Unity Catalog
Reading from an Iceberg Table
- Writing to a Wherobots-managed Catalog
- Writing to a new Managed Iceberg Table in Unity Catalog
Next steps
Try it in a notebook
Walk through a hands-on tutorial reading Unity Catalog Delta tables in Wherobots.
Usage and limitations
Review workflow use cases, catalog naming rules, and the foreign-catalog limit.
Federate AWS Glue Catalog
Connect another external data source with Wherobots Data Federation.
Data Federation overview
Learn how Wherobots queries external data sources in place.
Usage and limitations
- Catalog Naming: You cannot use a local alias for a catalog. If you have a pre-existing catalog in your Wherobots Organization named
wherobots, trying to connect a Databricks catalog with the namewherobotswill cause a permanent naming conflict and must be avoided. - Catalog Limit: The integration supports a limit of 10 foreign catalogs per Organization.
- UniForm: If you use Databricks’ Universal Format (UniForm) to enable Iceberg reads on a Delta table, that table will be read-only.

