OpenMetadata Catalog

v0.8.3 ships an OpenMetadata publish-side registrar — contracts can register themselves into an OpenMetadata server at apply / publish time so the catalog reflects the data product alongside the underlying tables.

Recommended for: teams running OpenMetadata as their data discovery / governance catalog, especially in stacks that already use OpenMetadata's lineage and glossary surfaces.

Publish-side only on this page

There is no source-side OpenMetadata read adapter on v0.10.0 — fluid forge data-model from-source does not (yet) include OpenMetadata in the seven catalogs supported by the source-side flow. If you need to forge a contract from OpenMetadata metadata, open an issue and we'll prioritise the read adapter.

Opt in

# contract.fluid.yaml
properties:
  catalog:
    register: [openmetadata]

Environment variables

Variable	Purpose
`FLUID_CATALOG_OPENMETADATA_URL`	OpenMetadata REST endpoint (e.g. `https://openmetadata.corp.example.com/api`).
`FLUID_CATALOG_OPENMETADATA_TOKEN`	OpenMetadata bearer token.

The publish-side path uses the canonical SSRF-guarded HTTP client. See network safety.

What gets emitted

Contract field	OpenMetadata entity
Output ports	`Table` per port (REST `PUT /v1/tables`)
Per-port schema	`Column` entries on the matching table
`metadata.layer` / `metadata.productType`	Extension fields on the table (canonical extension namespace)
`metadata.domain`	`Domain` (created if absent)
Tags / classifications	`Tag` entries surfaced via OpenMetadata's classification API

The registrar writes are idempotent — re-publishing the same contract is a no-op against OpenMetadata.

Verify a publish locally

export FLUID_CATALOG_OPENMETADATA_URL=https://openmetadata.local:8585/api
export FLUID_CATALOG_OPENMETADATA_TOKEN=$(cat ~/.openmetadata-pat)
fluid apply contract.fluid.yaml --yes
# → ... [publish] openmetadata: PUT /v1/tables (200)

If the registrar can't reach OpenMetadata, the publish step warns rather than fails the apply.