DataHub Release Notes for May 2025

New

We added these features

The Match Entities endpoint in the Repository API supports a new ambiguousMatchSampleSize query parameter that lets you specify the number of sample ambiguous matches to return when a match fails due to too many potential matches. The response includes detailed information such as matched entities, match rounds, and fuzzy match scores to help diagnose and refine match rules. This update improves transparency and accelerates testing and troubleshooting for complex match rules.

When you have an Ambiguous Match error, the entity transaction's Activity tab in the Quarantine user interface displays a list of 10 sample golden records that match the incoming entity. For more information on Ambiguous Match, refer to Match Entities and Quarantines . (HUB-6133)
DataHub prevents records from being left without attached sources as a result of model deployments. The following actions take place when you attempt to deploy a model with deleted sources, revert a source configuration that results in records lacking a source, or delete a single contributing source:
- DataHub logs all model deployment attempts and failures in the audit log.
- Before attempting a deployment, DataHub checks whether the deployment will remove the only contributing source.
- If DataHub prevents a deployment because it would remove the only contributing source linked to a record, DataHub displays an error message explaining the reason for the failure.
(HUB-6130)
In the platform, DataHub users, with the required prerequisites for Command Center, can now access Command Center from any DataHub page with the Command Center link instead of the tab. When the link is clicked, a new web browser tab opens with Command Center. For more information on getting started in Command Center, refer to Getting started in Command Center. (HUB-6097)
In the platform, DataHub users can now access Data Integration from any DataHub page. When the link is clicked, a new web browser tab opens with Data Integration. (HUB-6094)
If left blank or deleted, the field Maximum Text Length defaults to 100 characters. (HUB-6087)
USA East Hub Cloud 02 is now 4-byte UTF8 enabled for text/string fields. If your DataHub repository (where your golden records are stored) is hosted in this region, your golden records now also support supplemental 4-byte characters and symbols. This update also improves matching performance and accuracy.

4-byte UTF8 support will be rolled out to all existing Hub clouds in the near future, as the existing 3-byte encoding is currently deprecated. (HUB-3581)

note
Impact: This change affects your model size since text fields are now 4 bytes. Read Best practices for designing models for guidance on model size limitations.

Fix

We fixed these issues

For repositories with Accelerated Query enabled, DataHub now successfully restores quarantined, end-dated records that contain updated field values. Modified field values display accurately in the golden record view in the UI. (HUB-5744)
Channel updates are now correctly held when outbound integrity is enforced on reference fields, and the reference does not exist in the target source. Fetch operations no longer return held records as if they were active. (HUB-5322)
When a purge happens, a sync check occurs. If the number of records does not match, a resync is performed. (HUB-5635)
This update resolves an issue that caused record purging to fail when no record history was present. (HUB-5634)
Log messages with the same timestamp now have a set order. The log message stays on the same page as the user changes pages. (HUB-5611)
Historical metrics for transactions caught by Early Delta Detection are now available for all users with access to Historical Reporting. (HUB-5738)
The Status field in the Query Bulk Processing Requests API is now also returned when the bulk request has been canceled or an error is encountered. (HUB-5722)

Platform Release