1.7.1-release

Improvements

• Login page UI.
• DQ failure lineage tracing.
• Add Domain selection while creating tags.
• Added support for the Korean language.
• Support edit display name for the dashboard Data model.
• Configurable account usage for incremental metadata extraction.
• Add Athena schema comment support.
• Support dynamic height for detail page widgets.
• Add support for the following databases, schemas and services.
• Allow editing of SQL function at column level lineage.
• Support chart export in cost analysis.
• Add domain-level permissions while creating/updating dataProduct.
• Add support to add and edit Data Product from the entity page.
• Add bulk edit action for glossary listing page.

Fixes

• Severity of incident POST creation.
• Service insights PDF export.
• Can't run table diffs on Snowflake when using private key authentication.
• Self-signup login error is not showing.
• Service connection config is not getting updated with multiple project IDs after ingestion.
• Data assets order in the Explore left panel.
• Added display name and description in Testcase Alert emails.
• PostgreSQL schemas are getting filtered out.
• Make prompt=login as optional.
• Apps allowing submission of negative numbers for some config fields.
• Error connecting S3 container to pipeline or tables in lineage edit mode.
• Mentions on the task should trigger the @mention alert.
• Postgres Duplicate table constraint error when re-ingesting.
• Unsupported Pipeline entity for lineage error.
• Issue with refresh for loggedInUser returns 401.
• Render settings menu based on permissions.
• Data products are not visible when redirecting from the assets listing to the entity page.
• Make certification always visible.
• Dots are misaligned/unclear in the multi-metric view of Test Case Metrics.
• Snowflake Tags Not Reattached or Re-ingested After Initial Ingestion.
• Remove data products associated with the old domain when an entity's domain is updated.
• Multiple image insertion issue and ensure proper inline error messaging for the Rich Text Editor.
• Handle UDF definition fetch exceptions.
• Parquet endpoint null case error.
• The deleted user page shows a spinner instead of "User not found".
• The enum cleanup is not triggering when all enum keys are removed in the custom property.
• Inconsistent behaviour when reassigning an asset to a different domain via the bulkAsset API.
• Airbyte pipeline lineage extraction.
• Add an include field for the list incident API.
• Metadata ingestion errors from Azure Data Lake.
• Support Ingesting Multiple Owners for dbt Models from manifest.json.
• Error ingesting using Datalake ADLS connector.
• PostgreSQL Sample Data Err- FATAL: too many connections for role "role_name".
• Testcase "Column values to be unique- oracledb error (ORA-00937).
• Alert Triggering on Both Failure and Success of the Test Case, even if configured for failure only.
• PBI lineage when source parameters are used and the lineage needs to be created from source expression.
• Comments are not reflected after ingestion for DB columns in Vertica.
• Custom theme styling issues.
• Entity right panel collapsing issue.
• Feeds count not showing up in the PipelineDetails page.

1.6.12-release

pbi dashboard sourceurl fix (#21026)

1.6.11-release

add whats new for 1.6.11

1.6.10-release

Use Subset of Permissions for add delete Users in teams  (#20783)

* Use Subset of Permissions

* use correct permissino to show add user option

---------

Co-authored-by: Chirag Madlani <[email protected]>

1.7.0-release

The latest Release 1.7 of OpenMetadata and Collate delivers new features to accelerate the onboarding of both data services and users, taking discovery, automations, and customizations one step further.

Backward Incompatible Changes

Removing support for Python 3.8

Python 3.8 was officially EOL on 2024-10-07. Some of our dependencies have already
started removing support for higher versions, and are following suit to ensure we are using the latest and most stable
versions of our dependencies.

This means that for Release 1.7, the supported Python versions for the Ingestion Framework are 3.9, 3.10 and 3.11.

We were already shipping our Docker images with Python 3.10, so this change should not affect you if you are using our Docker images.
However, if you installed the openmetadata-ingestion package directly, please make sure to update your Python version to 3.9 or higher.

OpenSearch Settings Update

OpenSearch has a different default value of max_clause_count than Elasticsearch. This means that if you are using OpenSearch, you will need to update the max_clause_count setting in your OpenSearch configuration:

indices.query.bool.max_clause_count: 4096

If you're using AWS, you can add this setting from the console as well.

What's New

Automate Metadata Onboarding Instantly with OpenMetadata AutoPilot

Data teams often face manual, repetitive tasks onboarding new services—configuring workflows individually for schemas, lineage, usage, and profiling. This slows down onboarding and can cause inconsistent metadata coverage.

OpenMetadata’s AutoPilot makes onboarding effortless:

• Automated Workflows: Automatically triggers metadata extraction for schemas, lineage, usage, and profiling whenever a new service is added. No manual setup required.
• Optimized Filtering: Includes default filters for relevant metadata, with the flexibility to add custom filters, ensuring consistency and efficiency.
• Immediate Insights: Provides real-time KPIs on asset distribution, metadata coverage (descriptions, ownership), tiering, and PII tagging to proactively improve data governance.

Automate Documentation, Classification, and Data Quality with Collate AI Agents (Collate)

Collate is enhancing AutoPilot by integrating powerful AI Agents that automate critical metadata tasks—saving your team time and increasing metadata coverage instantly.

• Automated Tiering: The Tier Agent analyzes usage patterns and lineage to automatically identify the business-critical data assets within your organization.
• Intelligent Documentation: The Documentation Agent automatically generates accurate descriptions of your data assets and powers a seamless Text2SQL chat experience.
• Data Quality Automation: The Data Quality Agent intelligently creates Data Quality tests based on data constraints and learns from existing tests across similar datasets.

With Collate AI Agents in AutoPilot, it’s like adding expert team members who streamline metadata management—accelerating onboarding, improving governance, and freeing your team to focus on higher-value tasks.

Customize Your Data Discovery with Enhanced Search Relevancy Settings

As your data platform expands, quickly finding the most relevant data assets becomes essential. OpenMetadata already boosts search results based on business-criticality (Tiers) and usage patterns—but your organization’s preferences might vary.

With the new Search Relevancy Settings, OpenMetadata gives you complete control to tailor your discovery experience by:

• Fine-tuning searchable fields such as asset names, descriptions, or column details.
• Adjusting result boosting based on default properties like Tiers and usage, or adding custom tags to further enhance relevancy.
• Applying customized ranking across all data assets or specific asset types like Tables, Dashboards, or Topics.

Ensure users always discover the right data, quickly and intuitively, by customizing your search experience with OpenMetadata’s enhanced relevancy settings.

Navigate Your Data Ecosystem with Hierarchical Lineage

OpenMetadata’s enhanced Lineage UI in Release 1.7 introduces Hierarchical Lineage Layers, enabling teams to intuitively explore data lineage from a high-level overview down to granular details:

• Service Layer: Provides visibility into data flows between different platforms or services.
• Domain Layer: Clearly illustrates how data traverses across Data Mesh domains.
• Data Product Layer: Shows lineage across specific data products, aligning closely with business definitions.

Alongside these layers, column-level lineage remains easily accessible, helping teams precisely understand data transformations and impacts—simplifying root-cause analysis and governance decisions.

Simplify the User Experience with Persona-Based Customizations

OpenMetadata provides detailed information on your data assets—covering schema, lineage, data quality, and observability. But different user personas have different needs and workflows, and one size doesn’t fit all.

With Release 1.7, you can now fully personalize OpenMetadata’s user experience based on defined User Personas:

• Navigation Panel Customization: Tailor the navigation panel by adding, removing, or sorting elements to match the workflow of each persona.
• Data Assets & Governance Entities: Reorganize, add, or remove tabs and customize widget layouts—highlighting relevant custom properties, descriptions, or key insights specific to each persona.

Persona-based customization ensures each user sees only what’s relevant and important to their role—streamlining workflows, improving usability, and enhancing adoption across your organization.

Discover the Right Data Even Faster with an Enhanced UX

OpenMetadata is already known for its intuitive UI and simplified user experience. In Release 1.7, the UX is elevated further, making it even easier for diverse user personas to quickly find and act on the data they need.

Key UX improvements include:

• Streamlined Navigation: Simplified navigation panels to quickly guide users through key actions.
• Clearer Asset Information: Improved placement and labeling of critical information on data asset pages, ensuring immediate understanding.
• Enhanced User Profiles: Restructured user pages for better visibility into profile details and more intuitive management of open tasks.

Automatically Propagate Collate Metadata into Your Data Platforms (Collate)

Collate already simplifies capturing and managing metadata—tags, descriptions, and ownership—across your entire data ecosystem. But making sure this enriched metadata reaches back into your source systems is equally crucial.

With the new Reverse Metadata feature, you can:

• Automatically push centralized metadata from Collate directly back into your databases (MySQL, Postgres), warehouses (Snowflake, BigQuery), and dashboards (e.g., Power BI).
• Select which assets should synchronize, and your source systems will instantly receive metadata updates in real time.

This seamless, two-way metadata synchronization enables powerful governance use-cases—such as automating data masking policies in Snowflake based on centrally managed tags—and turns Collate into a single source of truth at the heart of your end-to-end automated governance strategy.

PNG & PDF Exports

Support for exporting Lineage and ER diagrams in PNG, and Data Quality, Data Insights, and more in PDF!

Bulk Edit Action

Enable bulk editing capabilities for Database, Schema, Table, and Column entities — allowing efficient management of multiple items simultaneously.

Recursive Import/Export

You can now import and export the entire entity hierarchy with all related data, including parent-child relationships and dependencies!

Asynchronous Deletion

Support for both soft and hard deletion operations across all services, entities, glossary, and term entries — improving overall performance.

1.6.9-release

Made Fields immutable for Applications (#20799)

* Made dropdown immutable for input field

* added tests

* removed test

1.7.0-rc2-release

fix: field value boost options (#20794)

1.6.8-release

What's Changed

Improvements:

• Added support for Wherescape connector.
• PowerBI owners ingestion for assets, improved filter query performance.
• REST connector enhancements.
• Implement column validation in lineage patch api.

Fixes:

• Fixed tableau ingestion for null upstream table queries.
• Fixed public schema lieage for postgres.
• Fixed IncidentManager date filtering and update table column title.
• Fixed dbt cloud latest run execution.
• Fixed Unpinned google-cloud-secret-manager version in ingestion dependencies.
• Fixed update query to fix domain asset update.
• Fixed DQ for local webserver.
• Fixed placeholder issue for empty metrics.

Full Changelog: 1.6.7-release...1.6.8-release

1.7.0-rc1-release

chore(release): Prepare Branch for `1.7.0-rc1`

1.6.7-release

What's Changed

Improvements:

• Lineage Improvements - Added Tableau Custom SQL lineage support
• Lineage Improvements - Added column count validation when creating table-type custom property
• Lineage Improvements - Transformed Reserved keywords like quotes to OM compatible
• Lineage Improvements - Added missing timestamp indexes for time series tables
• Lineage Improvements - Enhancing FQN Handling: Support for Quoted Identifiers

Fixes:

• Fixed potential Okta login issues by clearing state to avoid login errors
• Fixed MariaDB profiling with Time datatype
• Fixed handling of Sample Data with non-utf8 characters
• Fixed test connection showing timeout after successful connection
• Fixed DBT logs and improved error handling
• Fixed Test Suite 'NoneType' object has no attribute 'id' handling
• Fixed delete entity relation live indexing
• Fixed Data Insights Data Stream deletion on OpenSearch
• Fixed soft delete and restore functionality
• Corrected childrenCount for Organizations in Teams
• Fixed custom dashboard issue with term type of data
• Lower training window for Collate Anomaly detection model (collate)