← Back to all sparks
O

OpenMetadata

ANALYTICS
Velocity5.0

Unified metadata platform for data discovery and governance

OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.

data-cataloglineageconnectorsdata-qualitymcp
◆Current state
OpenMetadata is still in 2.0.x maintenance mode, shipping a release every one to two weeks. 2.0.8 on November 13 is the broadest yet: Hex and Sigma ingestion now build data models and column lineage, BigQuery date-sharded tables can be grouped into one logical table, Power BI and Snowflake ingestion stop leaving stale or runaway jobs, and MCP authentication and access controls were tightened. The 2.1.0 line sits at rc2, whose only published change is a tag-resolution fix.
◆Where it's heading
Each 2.0.x release repairs connectors and lineage that 2.0 left incomplete, and the fixes increasingly touch accuracy (correct table identity, lineage that ends at the right model) rather than crashes. MCP keeps appearing in the security sections, which suggests OpenMetadata expects AI tools to read the catalog and is locking that path down before 2.1.
◆Prediction
A 2.1.0 final is the next visible step, since two release candidates are out; the entries do not yet say what features 2.1 adds beyond the fixes backported to 2.0.x.

◆Recent moves

  1. 21h ago

    2.0.8: Hex and Sigma lineage, BigQuery shard grouping, MCP auth

    The largest 2.0.x maintenance release so far adds data models and column lineage for Hex and Sigma, groups BigQuery daily shards into one table, and tightens MCP authentication. It continues the pattern of making 2.0's connectors accurate rather than merely working.

    View source ↗
  2. 22h ago

    2.1.0 rc2: fix for tags removed when resolving tag tasks

    The second 2.1 candidate's notes cover a single cherry-picked fix: resolving a tag-update task no longer wipes the column's other tags. It moves 2.1 toward final without showing new features.

    View source ↗
  3. 14d ago

    2.1.0 rc1 appears, with notes covering only a UI fix

    The first 2.1 candidate marks the move past 2.0 maintenance. Its published notes describe only a dark-mode fix for settings surfaces, so the release's scope cannot be judged yet.

    View source ↗
  4. 17d ago

    2.0.7: Pub/Sub, SQL Server and Unity Catalog connector fixes

    Maintenance focused on connector reliability and search consistency, with Pub/Sub impersonation and SQL Server test timeouts fixed. It also strengthens governance workflows and access controls.

    View source ↗
  5. 23d ago

    2.0.6: ingestion accuracy, safer upgrades, multi-pod fixes

    Aims at trust in the data: more accurate ingestion, safer upgrades and Data Quality results that hold up, with multi-pod fixes and security patches alongside.

    View source ↗
  6. 1mo ago

    2.0.5 restores metadata lost to 2.0 ingestion regressions

    Restores metadata affected by 2.0 ingestion regressions and protects user-managed metadata during bot ingestion, plus Redshift datashare support on consumer clusters.

    View source ↗