Feature Request: Programmatic Column Description Patching via JSONPatch API

Resolved 💬 1 comment Opened Jun 24, 2026 by alcz86 Closed Jun 27, 2026

Summary

We need API-level support for patching column descriptions in table entities via JSONPatch.

Current behavior: Only table-level fields can be patched. Column descriptions are architecturally read-only via /api/v1/entities/{tableId} PATCH endpoint.

Desired behavior: JSONPatch operations should accept:

[{"op":"add","path":"/columns/0/description","value":"<p>Description</p>"}]

Use Case

Enterprise data governance: bulk-populating column metadata for data products via automation. Blocks OpenMetadata adoption as column SSOT.

Workarounds Tried & Failed

  • MCP patch_entity: 'Patch cannot be null or empty'
  • Direct REST PATCH: HTTP 404
  • PUT with full entity: HTTP 404

Acceptance Criteria

Any of: JSONPatch column support, bulk endpoint, first-class column entities, or BigQuery schema comment sync

Environment: OpenMetadata (BQ connector)

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗