Skip to main content

Latest Release Notes

20 November 2026
For more information, see the OpenMetadata 2.0.9 GitHub release.

Changelog

OpenMetadata 2.0.9 is a maintenance release that moves the server and Kubernetes operator images to Java 21.0.13.1, which fixes CVE-2026-114938. It also improves the MicroStrategy and Sigma connectors and makes profiling and sampling more reliable. The release fixes Data Quality, Data Insights, and governance workflow issues. It also improves search reindexing, alerts, upgrades, and user interface (UI) reliability.

🔌 Connectors and Ingestion

This release includes the following connector and ingestion improvements:
  • MicroStrategy ingestion was unreliable and lineage was incomplete #37730, #37855, #37945, #37980, #38217: The connector now skips documents, parses cube SQL once, and routes lineage by project. It adds column-level lineage from cube SQL to data models and reads a report dataset’s lineage from its source cube. Reports built on Live cubes now explain where their data comes from.
  • Sigma lineage was missing for elements and formulas #37766: Sigma ingestion now walks element lineage, lists workbooks across the whole organization, and captures formula lineage.
  • dbt meta could apply glossary terms that weren’t approved #37719: Only glossary terms in Approved status are applied from dbt meta.
  • Concurrent BigQuery datasets could share data definition language (DDL) cache entries #38234: The DDL cache is now keyed by fully qualified name.
  • SQL Server and Azure SQL profiler SQL altered schema names #37789: Literal schema names are now preserved.
  • Oracle percentage samples were inaccurate #37940: A new Oracle sampler keeps percentage samples per row.
  • The datalake sampler dropped rows and flattened lists #38175: Rows with partial nulls are kept, and list cells are returned as lists.
  • Google Cloud Storage (GCS) structured child container metrics were wrong #37968: Metrics for structured child containers are now computed correctly.
  • Testing a connection from the service page used the wrong runner #38159: The service’s configured runner is now sent.
  • Ingestion could install an incompatible python-liquid #37871: python-liquid is now capped below version 3.

📊 Data Quality and Data Insights

This release includes the following Data Quality and Data Insights fixes:
  • Data Quality table totals were inexact #37913: Exact table totals and related integration fixes are backported to 2.0.
  • The Open incident card undercounted incidents #38222: The card now counts Acknowledged and Assigned incidents, and incident cards are described as daily activity.
  • Metrics could show the wrong status, and the metrics worker could race #38009, #37899, #38130: The metrics list shows the real status, and the worker finishes in-flight items before summarizing or resetting for a new run.
  • Data Insights charts drew axis categories they didn’t count #37898: The categorical axis is now drawn only from the documents the chart counts. A new DataInsightsExtension hook is also available #37815.

🛡️ Data Governance and Workflows

This release includes the following governance and workflow fixes:
  • Resolved tag updates left stale tags behind #37724: Tags that a resolved tag update leaves out are now removed.
  • Tag recognizers could be saved without a supported language #37568: These recognizers are now rejected.
  • Tag suggestion tasks were displayed as description tasks #38114: Tag suggestion tasks now display as tags.
  • A hard delete removed the tags of entities that share its fully qualified name #38230: Tags on other entities with the same fully qualified name are now kept.
  • Undone edits could hang workflows, and tag renames with backslashes left a stale cache #38225: Both issues are fixed.
  • Workflow node factories were hard-coded #38141: Factories are now discovered from the classpath.
  • Lifecycle-only updates changed the version author #37995: The original author is now kept.
  • CSV imports dropped rows and versions #38192: Imported rows and their versions are now kept.
  • Task-created notifications linked to the wrong place #38090: Notifications now link to the task page.

🔗 AI Context and MCP Server

This release includes the following Model Context Protocol (MCP) fixes:
  • Disabling the MCP Server application required a restart #37727: MCP now stops as soon as the application is disabled.
  • get_entity_details calls without entityType or fqn failed unclearly #38160: These requests are now rejected with a 400 response.

🔍 Search and Discovery

This release includes the following search fix:
  • The orphan sweep could fail a live reindex job #38120: The sweep no longer fails a reindex job while it initializes.

📣 Alerts and Events

This release includes the following alert fix:
  • Opening an alert’s page could load an unbounded number of pending events #38094: The pending count is now capped and shows “500+” when there are more.

⚙️ Platform and Operations

This release includes the following platform and operations fixes:
  • The 2.0.8 audit log cleanup could run for hours on large installations #38153: The audit log entity-type index is now created before the cleanup runs.
  • The bundled MySQL image used end-of-life MySQL 8.0 #38172: The bundled image now ships MySQL 8.4.13, which is also used in testing. MySQL 8.0 is still supported as an ingestion source.
  • Okta Security Assertion Markup Language (SAML) certificates whose common name is the organization name were rejected #33625: These certificates are now accepted.
  • Signup and password-reset flows hid email delivery failures #38232: The 424 FAILED_SEND_EMAIL response is now preserved.

🎛️ UI

This release includes the following UI fixes:
  • Composite unique constraints were indistinguishable #38178: Composite unique constraints are now shown distinctly.
  • The My Tasks widget rendered every card at once #37944: Cards now mount only when scrolled into view.
  • Context Center article tabs were narrow #38193: Article tabs are now full width, and AskCollate is dropped from the memories subtitle.

🔒 Security

This release includes the following security update:
  • The bundled JDK was affected by CVE-2026-114938 (“Java4Shell”) #38125: The server, Kubernetes operator, and Resource Description Framework (RDF) store (Fuseki) images now use Amazon Corretto 21.0.13.1.2, which includes the fix. Only servers on x86-64 CPUs with AVX-512 VBMI running Java older than 21.0.13.1 were affected. ARM hosts were not. If you can’t upgrade right away, set OPENMETADATA_OPTS="-XX:-UseBASE64Intrinsics" on the server and restart.