Skip to content

Releases: open-metadata/OpenMetadata

OpenMetadata 0.10.1-release

18 May 06:58
Compare
Choose a tag to compare

What's Changed

  • 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 (#4988) by @vivekratnavel in #4989

New Contributors

Full Changelog: 0.10.0-release...0.10.1-release

OpenMetadata 0.10.0-release

26 Apr 17:33
5200834
Compare
Choose a tag to compare

What's Changed

Support for Database Schema

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.

Support for Hard Delete

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.

Deploy Ingestion from UI

OpenMetadata has refactored the service connections to simplify the ingestion jobs from both the ingestion framework as well as 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.

Download DBT Manifest Files from Amazon S3 or Google Cloud Storage

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.

JSON Schema based Connection Definition

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.

Airflow Rest APIs

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.

UI Changes

  • The UI improvements are directed towards 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.

Security Changes

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 the 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 as well as on the ingestion side.

Azure SSO

Support has been added for Azure SSO on Airflow.

New Contributors

Full Changelog: 0.8.1-release...0.10.0-release

OpenMetadata 0.9.1-release

08 Apr 14:20
Compare
Choose a tag to compare

Collaboration

  • Conversations in the main feed
  • Users can ask each other questions, add suggestions and replies
  • Table details - Click through on usage to see who or what services are using it, and what queries are pulling from it.

Data Quality

  • Ability to create and monitor the test cases
  • Data Quality Tests support with Json Schemas and APIs
  • UI Integration to enable users to write tests and run them on Airflow

Glossary

  • 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

Connectors

  • 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

Lineage

  • DataSource SQL Parsing support to extract Lineage
  • View Lineage support

Pipeline

  • Capture pipeline status as it happens

Security

  • Security policies through the UI
  • Configuration personas and authorization based on policies
  • AWS SSO support

New Contributors

Full Changelog: 0.8.1-release...0.9.1-release

OpenMetadata 0.9.0-release

10 Mar 19:25
Compare
Choose a tag to compare

What's Changed

Read more

OpenMetadata 0.8.4-release

23 Feb 12:53
Compare
Choose a tag to compare

This is a bug fix release for #2940.

OpenMetadata 0.8.3-release

21 Feb 07:38
Compare
Choose a tag to compare

This is a bug fix release for the #2490.

OpenMetadata 0.8.2-release

18 Feb 21:05
Compare
Choose a tag to compare

This is a bug fix release for the #2843

OpenMetadata 0.8.1-release

18 Feb 20:41
647712c
Compare
Choose a tag to compare

This is a bug fix release for the #2843

OpenMetadata 0.8.0-release

25 Jan 20:10
Compare
Choose a tag to compare

Access Control Policy

  • New entities called ‘Role’ and ‘Policy’ have been added.
  • A User has a ‘Role’. A ‘Policy’ can be assigned to a Role.
  • A Policy has a set of ‘Rules’. Rules are used to provide access to functions like updateDescription, updateTags, updateOwner and so on.
  • Can provide access to metadata operations on any entity.
  • A standard set of Roles with their Policies have been added in the new release.
  • ‘Admins’ and ‘Bots’ can perform any metadata operation on any entity.
  • Admins can define policies through the Policy UI, and assign roles to the Users.

Manual Lineage

  • Enhance the lineage captured from machine metadata with user knowledge.
  • Users can edit the lineage and connect the entities with a no-code editor.
  • Drag and drop UI has been designed to add lineage information manually for the table and column levels.
  • Entities like table, pipeline, and dashboard can be dragged and dropped to the lineage graph to create a node.
  • The required entity can be searched and clicked to insert into the graph.

Event Notification via Webhooks & Slack Integration

  • Subscribe event notifications via webhooks.
  • Send metadata change events as Slack notifications
  • Provide timely updates to keep the data team informed of changes

Entity Deletion

  • API support has been added for entity deletion, both for soft delete and hard delete.
  • A deleted dataset is marked as deactivated in the OpenMetadata backend instead of hard deleting it.
  • Ingestion support has been added to publish entity deletion.
  • Enabled version support for deleted entities.

Version panel has been added for all the entities- Table, Topic, Pipeline, and Dashboard.

  • Previously, we were getting the change descriptions for a limited set of fields for the Topic entity; several other fields have now been included.

New Connectors

  • Supports Delta Lake, an open source project that enables building a Lakehouse architecture on top of data lakes.
  • Worked on the refactor of SQL connectors to extract the lineage.
  • Connector API was refactored to capture the configs on the OpenMetadata side and to schedule the ingestion via UI.

Other Features

  • DataSource attribute has been added to the ML model entity.
  • Python API has been updated to add lineage for ML Model entities.
  • A new tab called ‘Bots’ has been added to group users with isBot set to true.
  • Support Application Default Credentials or a keyless, default service account in BigQuery data ingestion.
  • Includes a feature tour for new users.

OpenMetadata 0.7.1 Release - Bug Fix

10 Jan 22:33
Compare
Choose a tag to compare
  1. Fixed migrate issue for ./bootstrap-storage.sh migrate-all
  2. Fixed sql v2 file to drop if exists on dbt_table_entity