mcp-data-platform-v1.44.2
apply_knowledge Write Fixes (Part 2)
Bumps txn2/mcp-datahub from v1.4.1 to v1.4.2, fixing the four remaining apply_knowledge write failures discovered during live verification. Pure dependency bump — no platform code changes.
This completes the DataHub 1.4.x write support. All apply_knowledge change types now work against all advertised entity types.
Dependency Update
| Dependency | Previous | New |
|---|---|---|
txn2/mcp-datahub |
v1.4.1 | v1.4.2 |
Bug Fixes
1. set_structured_property — Wrong GraphQL field name
The upstream mutation input used propertyUrn (the REST API field name) instead of structuredPropertyUrn (the GraphQL field name). Every set_structured_property call failed with field name 'propertyUrn' is not defined for input object type 'StructuredPropertyInputParams'.
Before (v1.44.1): set_structured_property failed on all entities.
After: Structured properties are set successfully.
2. resolve_incident — Wrong GraphQL input type
The upstream mutation declared $input: UpdateIncidentStatusInput! but DataHub 1.4.x renamed the type to IncidentStatusInput!. Every resolve_incident call failed with a type mismatch validation error.
Before (v1.44.1): resolve_incident failed on all entities.
After: Incidents are resolved successfully.
3. update_description on domain/glossaryTerm/glossaryNode — REST API limitation
The REST ingestProposal endpoint does not register domainProperties, glossaryTermInfo, or glossaryNodeInfo as writable aspects, returning 422 validation errors. The upstream client now routes these entity types through the GraphQL updateDescription mutation instead.
Before (v1.44.1): update_description failed on domain, glossaryTerm, and glossaryNode entities.
After: Descriptions update successfully via GraphQL.
4. add_tag / remove_tag / add_glossary_term on domain/glossaryTerm/glossaryNode — Same REST limitation
The REST API does not register globalTags or glossaryTerms as writable aspects for these entity types. The upstream client now routes them through GraphQL addTag/removeTag/addTerm/removeTerm mutations. All other entity types (dataset, dashboard, chart, etc.) continue using REST unchanged.
Before (v1.44.1): Tag and glossary term operations failed on domain, glossaryTerm, and glossaryNode entities.
After: All operations work via GraphQL.
Complete Write Support Matrix (as of v1.44.2)
All apply_knowledge change types now work on all advertised entity types:
| Operation | dataset | dashboard | chart | dataFlow | dataJob | container | dataProduct | domain | glossaryTerm | glossaryNode |
|---|---|---|---|---|---|---|---|---|---|---|
update_description |
v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.2 | v1.44.2 | v1.44.2 |
add_tag / remove_tag |
v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.2 | v1.44.2 | v1.44.2 |
add_glossary_term |
v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.0 | v1.44.2 | v1.44.2 | v1.44.2 |
set_structured_property |
v1.44.2 | |||||||||
remove_structured_property |
v1.44.2 | |||||||||
raise_incident |
v1.44.1 | |||||||||
resolve_incident |
v1.44.2 | |||||||||
add_curated_query |
v1.44.0 |
Upgrade Notes
- No breaking changes. Drop-in replacement for v1.44.1.
- No configuration changes required.
- Recommended for all DataHub 1.4.x users. This release completes write support for all advertised change types and entity types.
Installation
Homebrew (macOS)
brew install txn2/tap/mcp-data-platformClaude Code CLI
claude mcp add mcp-data-platform -- mcp-data-platformDocker
docker pull ghcr.io/txn2/mcp-data-platform:v1.44.2Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-data-platform_1.44.2_linux_amd64.tar.gz.sigstore.json \
mcp-data-platform_1.44.2_linux_amd64.tar.gz