Releases

Note

The OpenMetadata community is on a monthly release cadence. At every 4-5 weeks we will be releasing a new version. To see what's coming in next releases, please check our Roadmap section.

0.12.0 Release - Sept 7th 2022 🎉

You can read the Release Blog here or watch an awesome video showing the new features!



Prior releases supported a flat hierarchy of just Teams and Users. In 0.12, support has been added for the entire organizational hierarchy with Business Unit, Division, Department, and Groups. An organization from small to very large can now be modeled in OpenMetadata with this feature.

Access Control functionality has been revamped to support many use cases that were not possible before. Previously, a Role contained a single Policy, which consisted of simple Rules to Allow/Not Allow. The advanced rule configuration in the 0.12 release allows users to build more expressive rules using conditions.

  • A Role is a collection of Policies. Roles can be assigned to users or teams where all the users in the team inherit the team roles.
  • A Policy is a collection of Rules. A Policy can be reused as it can be part of a Role or can be directly assigned to Teams.
  • A Rule is defined by a set of Resources, a set of Operations, an Effect to either Deny or Allow the operation, and a condition written as SpEL expression to add additional conditions based on metadata attributes. Examples of conditions — isOwner(), noOwner() && !matchTags('PII').

OpenMetadata began support for Data Quality in the 0.10 release, and support was added for publishing Great Expectations results in the 0.11 release. Our goal with OpenMetadata is to define metadata standards for all things data and in this release, we are standardizing Tests and Data Quality metadata. Data Quality Tests can be expressed in JSON schema and now these tests can be added dynamically using the Test Definitions API. We have also added a custom SQL data quality test that allows you to write your data quality tests using SQL statements.

An interactive dashboard helps to visualize and explore the data from the Data Profiler. You can explore how your data is changing over time, and identify data drifts using this dashboard. You can also see how data quality is changing by looking at how tests are doing over time. What is even better is, that you can explore this at both the table level or drill down to each column level going back up to 60 days.

The UI supports the detailed exploration of data quality tests, and users can drill down for the details of the test results present in a time series fashion. Tests can be added easily from the Profiler tab in the UI, both at the Table and Column levels. The UI provides a one-glance update on the metrics with a summary of data quality at the Table and Column levels.

Informing users about upcoming changes to the data is a big challenge. In most organizations, a team sends an email well in advance about the change. But no one reads/tracks them and finally, when the change is done, many users are unprepared to handle it.

With Announcements, you can now inform your entire team of all the upcoming events and changes, such as deprecation, deletion, or schema changes. These announcements can be scheduled with a start date and an end date. All the users following your data are not only notified in Activity Feeds but a banner is also shown on the data asset details page for users to discover (or be reminded of) the announcement.

In 0.12, we’ve also streamlined the Notifications menu with two separate tabs for Tasks and Mentions, that’ll display only the recent notifications. You can always navigate to your User Profile page to view more activities.

Users can get timely updates about the metadata change events for all entities through APIs using webhooks. The webhook integration with Slack has been further improved in this release.

OpenMetadata also supports webhook integration to Microsoft Teams, just as it supports Slack. Users can choose to receive notifications for only the required entities by using event filters based on when an entity is created, updated, or deleted.

In the 0.11 release, a request to add or update descriptions for data assets could be converted to a Task. In the 0.12 release, Tasks can be created based on requests to create or update tags. Also, a glossary term approval workflow can be converted to a Task.

In 0.12, we have completely revamped how that secret is stored, accessed, and by whom; by introducing a Secrets Manager Interface to communicate with any Key Management Store. The KMS will mediate between any OpenMetadata internal requirement and sensitive information. That way, users can choose to use the underlying database as KMS, or any external system. The OpenMetadata community has already added support for AWS Key Management Service and AWS SSM.

New connectors are an essential part of every release in OpenMetadata. We are introducing four new connectors in this release:

  • Redpanda is a Kafka API-compatible streaming data platform for developers that unifies historical and real-time data. OpenMetadata now supports Redpanda as a Messaging service, which allows users to document its topics and schemas. Refer to the Redpanda documentation for more info.
  • Dagster is a new-generation Python-based orchestrator that’s designed for developing and maintaining data assets, such as tables, data sets, machine learning models, and reports. It has been added as part of OpenMetadata’s pipeline connectors. Read more from the Dagster documentation.
  • Fivetran delivers ready-to-use connectors that automatically adapt as schemas and APIs change, ensuring consistent, reliable access to data. It has been added as a pipeline service. For more information, refer to the Fivetran documentation.
  • Apache NiFi automates the flow of data between systems. OpenMetadata now supports a NiFi connector as the third new pipeline service on this release.

We’ve enhanced the performance of workflows by having a separate workflow for Lineage and Usage. By using two workflows for computing specific pieces of information, we can effectively filter down the queries to extract lineage.

During table usage ingestion, the tables retrieved successfully will be cached, so that there is no need to repeat the same calls multiple times as many queries would be referencing the same tables. Usage queries have been optimized. A result limit has been added to Usage queries.

The OpenMetadata Settings dropdown menu has been transformed into a single, centralized Settings page for added convenience in viewing all the available options. The Global Settings comprises setting options for Team Members, Access based on Roles and Policies, Services, Data Quality, Collaboration, Custom Attributes, and Integrations for webhooks and bots. Admins can view or update settings for various services like Slack, MS Teams, Webhooks, etc from the Global Settings page.

The major UI UX improvements have been done around Roles and Policies and a Global Settings page. Quite a lot of tweaks have been made to the UI to improve the UX.

When creating a new user or when a user is registering for the first time, the dropdown menu for Teams now displays an option to ‘Show All’ teams. Previously, we supported the display of only the first 10 teams. An option has also been provided to search and filter. UI improvements have been made on the Schema, Service, and Database details pages. Manage Tab has been replaced with the manage button on the UI.

  • Support for Postgres as OpenMetadata Store #4601
  • UI Improvements in 0.10.1 Release #4600
  • Support JWT Token Generation for Bot Accounts #4637
  • UI Ingestion Improvements - Support for Dashboards & Messaging Services #4843
  • Security: Fix Azure SSO and support refresh tokens in #4989

OpenMetadata supports databases, service name databases, and tables. We’ve added Database Schema as part of the FQN. For each external data source, we ingest the database, as well as the tables that are contained underneath the schemas.

OpenMetadata supported soft deletions. Now, we also support the hard deletion of entities through the UI, APIs, and ingestion. Hard deleting an entity removes the entity and all of its relationships. This will also generate a change event.

OpenMetadata has refactored the service connections to simplify the ingestion jobs from both the ingestion framework and the UI. We now use the pydantic models automatically generated from the JSON schemas for the connection definition. The ‘Add Service’ form is automatically generated in the UI based on the JSON schema specifications for the various connectors that are supported in OpenMetadata.

Previously, when ingesting the models and lineage from DBT, we passed the path of the DBT manifest and catalog files directly into the workflow. We’ve worked on improving the quality of life of DBT. Now, we can dynamically download these files from Amazon S3 or Google Cloud Storage. This way we can have any other process to connect to the DBT, extract the catalog, and put it into any cloud service. We just need the path name and workflow job details from the metadata extraction to be able to ingest metadata.

Each service (database, dashboard, messaging, or pipeline service) has its own configuration specifications, with some unique requirements for some services. Instead of the ad hoc definitions of the source module in Python for each connector, we’ve worked on the full refactoring of the ingestion framework. We now use the pydantic models automatically generated from the JSON schemas for the connection definition.

The Airflow REST APIs have been refactored. With our API centric model, we are creating a custom airflow rest API directly on top of Airflow using plugins. This passes the connection information to automatically generate all the dags and prepares handy methods to help us test the connection to the source before creating the service.

  • The UI improvements are directed toward providing a consistent user experience.
  • Hard Deletion of Entities: With the support for the hard deletion of entities, we can permanently delete tables, topics, or services. When the entity is hard deleted, the entity and all its relationships are removed. This generates an ‘EntityDeleted’ change event.
  • Dynamic “Add Service” Forms: The ‘Add Service’ form is automatically generated in the UI based on the JSON schema specifications for the various connectors that are supported in OpenMetadata.
  • UI Support for Database Schema as part of FQN: The database schema has been introduced in the 0.10 release. All the entity pages now support Database Schema in the UI.
  • Lineage Editor: Improvements have been made to the lineage editor.
  • Teams: While signing up in OpenMetadata, the teams with restricted access are hidden and only the joinable teams are displayed.
  • Team Owner: An Owner field has been added to the Team entity. Only team owners can update the teams.
  • Activity Feeds: The Activity Feeds UI supports infinite scrolling.
  • Add User: A user can be added from the Users page.
  • Support Refresh Tokens for Auth0 and Okta SSO: The JWT tokens generated by the SSO providers expire by default in about an hour, making the user re-login often. In this release, we’ve added support for refresh tokens for Auth0 and Okta SSO. The tokens are refreshed silently behind the scenes to provide an uninterrupted user experience. In future releases, we’ll continue to stabilize authentication and add refresh tokens for the other SSO providers.
  • Custom OIDC SSO: OpenMetadata now supports integration with your custom-built OIDC SSO for authentication. This is supported both on the front end for user authentication and on the ingestion side.
  • Azure SSO: Support has been added for Azure SSO on Airflow.
  • Conversations in the main feed.
  • Users can ask each other questions, add suggestions and replies.
  • Turn some threads into tasks and provide it in MyData as number of tasks.
  • Glossary.
  • Table details - Click through on usage to see who or what services are using it, what queries are pulling from it.
  • Ability to create and monitor the test cases.
  • Data Quality Tests support with Json Schemas and APIs.
  • UI Integration to enable user to write tests and run them on Airflow.
  • Glossaries are a Controlled Vocabulary in an organization used to define the concepts and terminologies specific to a particular domain.
  • API & Schemas to support Glossary.
  • UI support to add Glossary and Glossary Terms.
  • Support for using Glossary terms to annotate Entities and Search using Glossary Terms.
  • Apache Iceberg
  • Azure SQL
  • Clickhouse
  • Clickhouse Usage
  • Databricks
  • Databricks Usage
  • Delta Lake
  • DynamoDB
  • IBM DB2
  • Power BI
  • MSSQL Usage
  • SingleStore
  • Apache Atlas ,Import Metadata from Apache Atlas into OpenMetadata
  • Amundsen, Import Metadata from Amundsen into OpenMetadata
  • DataSource SQL Parsing support to extract Lineage
  • View Lineage support
  • Capture pipeline status as it happens
  • Security policies through the UI.
  • Configuration personas and authorization based on policies.
  • AWS SSO support.
  • Design of Access Control Policies.
  • Provide Role based access control with community feedback.
  • Register webhooks to get metadata event notifications.
  • Metadata Change Event integration into Slack and framework for integration into other services such as Kafka or other Notification frameworks
  • Delta Lake
  • Iceberg
  • PowerBI
  • Azure SQL
  • Users will have access to Activity Feed of all the changes to the Metadata.
  • New and Improved UX for Search and Landing page.
  • Extract Location information from Glue, Redshift.
  • Show Location details on the Table Page.
  • Support SSL (including self-signed certs) enabled ElasticSearch.
  • New entities will be indexed into ElasticSearch directly
  • Metabase
  • Apache Druid
  • Glue Improvements
  • MSSQL - SSL support
  • Apache Atlas Import connector
  • Amundsen Import connector
  • Metadata Change Event integration into Slack and framework for integration into other services such as Kafka or other Notification frameworks
  • Delta Lake support, Databricks, Iceberg
  • Capture changes to Entity Metadata from source and user interactions as versions.
  • Versioned changes will be published as events for clients to consume to take actions on.
  • Improvements to Data Reliability library.
  • Capture custom measurements through user provided SQL.
  • Airflow APIs to deploy DAGS and manage them.
  • UI integration to deploy ingestion workflows.
  • AWS Glue
  • DBT
  • MariaDB
  • Lineage related schemas and APIs.
  • Lineage metadata integration from AirFlow for tables.
  • UI changes to show lineage information to the users.
  • Improvements to Data Profiler.
  • UI integration with Data Profiler to show how the table profile looks over the period of time.
  • Support complex types such as Struct, Array with nested fields.
  • UI support to add expand complex types and tag, add description for nested fields.
  • Trino
  • Redash
  • Pipeline Entities are supported.
  • Integration with Airflow to extract Pipeline details.
  • Support for Message Service and Topic entities in schemas, APIs, and UI.
  • Kafka connector and ingestion support for Confluent Schema Registry.
  • Support for Dashboard services, Dashboards, and Charts entities in schemas, APIs, and UI.
  • Looker, Superset, Tableau connector, and ingestion support.
  • Sort search results based on Usage, Relevance, and Last updated time.
  • Search string highlighted in search results.
  • Support for Kafka and Dashboards from Looker, Superset, and Tableau.
  • Pluggable SSO integration - Auth0 support.
  • Support for Presto.
  • Salesforce CRM connector.
  • Data profiler to profile tables in ingestion framework and show it table details page.

Still have questions?

You can take a look at our Q&A or reach out to us in Slack

Was this page helpful?

editSuggest edits