Skip to main content
Feedback

Data Hub Release Notes for May 2026

Platform Release

May 30 2026

Data Hub features and fixes are not in the Runtime release.

New
We added these features

  • The Data Hub Repository API OpenAPI specification is now available for download. You can use the spec with tools such as Postman to explore available endpoints, generate sample requests and responses, and build integrations against the Data Hub REST APIs. Refer to the Data Hub Repository API Reference to learn more.

  • You can now retrieve Golden Record profiling statistics via API. The new endpoint returns the most recent available stats, and historical data is available for up to 60 days. (HUB-6414)

  • Error messages returned by the Get Universe Profile API have been updated to align with those of the v1 profile handler, improving consistency across API versions. (HUB-8242)

Fix
We fixed these issues

  • The Get Model API no longer returns collection keys for collections identified by occurrence. Additionally, collection keys are now properly removed when a collection's identification method is changed from Identified by Key to Occurrence. (HUB-7449)

  • The DataHub connector's Query Golden Records operation now correctly generates a response profile with maxOccurs=unbounded for the links element. Previously, the profile was generated with maxOccurs=1, limiting access to only the first link when multiple sources were configured. (HUB-7545)

  • The DataHub connector's Get Quarantine Entry operation now correctly maps the sourceEntityId attribute in the generated response profile. Previously, the profile used entityId, leaving the attribute unpopulated in responses. (HUB-7954)

  • Resolved a race condition in high-volume batch processing where an entity moved to a different batch during a merge could cause an unexpected error. The error is now handled gracefully. (HUB-7693)

  • Resolved an issue where unlinking a source from a reference record left orphaned reference links for other contributing sources. This prevented the reference field from being populated correctly on subsequent contributions. (HUB-8280)