Skip to main content

​
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

CatalogWhat’s SyncedAuth
AWS GlueDatabase, table, schema, partition spec, locationIAM role / access keys
Apache AtlasEntity, schema, lineage, classificationsKerberos / basic auth
CollibraAsset, schema, attributes, domain mappingAPI key
AlationData source, schema, table, column descriptionsAPI token
Unity CatalogCatalog, schema, table, storage locationService principal

​
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

POST /api/managed-lakehouse/tables/{tableId}/catalog-targets

{
  "catalogType": "glue",
  "catalogName": "production-glue",
  "config": {
    "region": "us-east-1",
    "database": "analytics",
    "roleArn": "arn:aws:iam::123456789012:role/GlueSyncRole"
  },
  "enabled": true
}

​
List Targets

GET /api/managed-lakehouse/tables/{tableId}/catalog-targets

​
Remove a Target

DELETE /api/managed-lakehouse/tables/{tableId}/catalog-targets/{targetId}

​
Sync Behavior

After every successful commit to a managed lakehouse table, the post-commit hook:
  1. Retrieves the list of enabled catalog targets for the table
  2. Builds a metadata payload (table name, schema, location, partition spec, snapshot ID)
  3. Sends the payload to each target in parallel
  4. Records sync status per target: synced, failed, or pending

​
Monitoring Sync Status

Each catalog target shows its last sync status in the Table Explorer:
StatusMeaning
syncedLast commit was successfully synced
pendingSync has not yet run
failedLast sync attempt failed — check error details
Failed syncs include an error message. The next pipeline commit retries the sync automatically.

​
Tier Availability

TierCatalog Targets per Table
Professional—
Premium2
EnterpriseUnlimited

Hosted Iceberg Catalog

The built-in catalog for direct query engine access

Data Catalog

Planasonix’s internal data catalog for discovery