Overview
Multi-Catalog Sync pushes table metadata from your Managed Lakehouse to external catalog systems after each commit. This keeps external discovery tools — AWS Glue, Apache Atlas, Collibra, Alation, and Databricks Unity Catalog — in sync without manual registration.Supported Catalogs
Configuration
Add a Sync Target
In the Table Explorer, navigate to the Catalog Sync tab:1
Click Add Catalog Target
Select the catalog type from the dropdown (Glue, Atlas, Collibra, Alation, Unity).
2
Name the target
Give it a descriptive name, e.g.,
production-glue or analytics-atlas.3
Provide credentials
Enter the connection details specific to the catalog type (IAM role, API key, service principal, etc.).
4
Enable
Toggle the target to active. Metadata will sync on the next pipeline commit.
API Configuration
List Targets
Remove a Target
Sync Behavior
After every successful commit to a managed lakehouse table, the post-commit hook:- Retrieves the list of enabled catalog targets for the table
- Builds a metadata payload (table name, schema, location, partition spec, snapshot ID)
- Sends the payload to each target in parallel
- Records sync status per target:
synced,failed, orpending
Monitoring Sync Status
Each catalog target shows its last sync status in the Table Explorer:
Failed syncs include an error message. The next pipeline commit retries the sync automatically.
Tier Availability
Related
Hosted Iceberg Catalog
The built-in catalog for direct query engine access
Data Catalog
Planasonix’s internal data catalog for discovery