DataHub 1.9.0, released on 16 November 2026, is the kind of software release whose important changes are scattered across defaults, compatibility, and edge-case behavior. The headline is not one new feature. It is the number of things an operator may need to notice before treating the upgrade as routine.
The most visible default changes are in metrics. METRICS_ENABLED now defaults to true; the release says this enables the Metrics page, the /metrics route, and backend wiring for Metric and Semantic Model. In version 1.8.0 the default was false, and the new behavior can still be disabled explicitly. That is a small configuration change with a large review consequence: a deployment can behave differently without anyone adding a new setting.
The sharper compatibility boundary is search. DataHub 1.9.0 no longer supports Elasticsearch 7.x and directs users to Elasticsearch 8.x or OpenSearch 2.x or 3.x. The same section lists changes to search V3 keyword scoring, default query fields, indexed fields, lineage and browse templates, and the default refresh interval for timeseries indices, now 60 seconds. The release links separate breaking-change guidance; the release page does not provide a deployment test or predict how a particular installation's results will change.
There is also a concrete boundary around system-client credentials. A client created without a token sends DATAHUB_SYSTEM_CLIENT_ID and DATAHUB_SYSTEM_CLIENT_SECRET only to the server configured by DATAHUB_GMS_URL. UI-managed ingestion refuses recipes that would send those credentials elsewhere. The release documents this as a routing restriction; it does not provide evidence for a broader claim about security outcomes.
Several smaller changes are worth reading in the same light:
- Google Drive ingestion is listed as Alpha, producing searchable Document entities.
- A recipe-probe command checks what a recipe would ingest before a run.
- The UI Rollback button and
datahub ingest rollback --nukeno longer delete an entity after another run or a user has written to it. - Other compatibility notes cover Airflow plugin dataset URNs, semantic-model treatment, and removal of the cloud pip extra.
That makes 1.9.0 less a feature-list upgrade than a review exercise. Before upgrading, the useful questions are concrete: which search backend and version is in use, what will the metrics default expose, where can ingestion credentials travel, and what does rollback mean after later writes? The official release page answers those questions at the change-log level and points to the detailed breaking-change document. It does not claim adoption, performance gains, or production results—and neither should the release note.