Open Standard for Metadata. A Single place to Discover, Collaborate and Get your data right.
APACHE-2.0 License
Published by Vj-L about 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.11.2-release...0.11.3-release
Published by akash-jain-10 over 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.11.1-release...0.11.2-release
Published by Vj-L over 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.11.0-release...0.11.1-release
Published by Rabi-Sahoo over 2 years ago
Data Collaboration has been the prime focus of the 0.11 Release, the groundwork for which has been laid in the past several releases. In the 0.9 release, we introduced Activity Feeds, Conversation Threads, and the ability to request descriptions. In this release, we’ve added Tasks, as an extension to the ability to create conversations and post replies.
We are particularly excited about the ability to suggest tasks. This brings the collaboration to the next level where an organization can crowdsource the knowledge and continuously improve descriptions.
https://github.com/open-metadata/OpenMetadata/issues/2931
In OpenMetadata, we primarily compute column-level lineage through SQL query analysis. Lineage information is consolidated from various sources, such as ETL pipelines, DBT, query analysis, and so on. In the backend, we’ve added column-level lineage API support. The UI now supports exploring this rich column-level lineage for understanding the relationship between tables and performing impact analysis. While exploring the lineage, users can manually edit both the table and column level lineage to capture any information that is not automatically surfaced.
The key goal of the OpenMetadata project is to define Open Metadata Standards to make metadata centralized, easily shareable, and make tool interoperability easier. We take a schema-first approach for strongly typed metadata types and entities modeled using JSON schema as follows:
OpenMetadata now supports adding new types and extending entities when organizations need to capture custom metadata. New types and custom fields can be added to entities either using API or in OpenMetadata UI. This extensibility is based on JSON schema and hence has all the benefits of strong typing, rich constraints, documentation, and automatic validation similar to the core OpenMetadata schemas.
Users can search by multiple parameters to narrow down the search results. Separate advanced search options are available for Tables, Topics, Dashboards, Pipelines, and ML Models. All these entities are searchable by common search options such as Owner, Tag, and Service.
The Glossary UI has been upgraded. However, the existing glossary functionality remains the same, with the ability to add Glossary, Terms, Tags, Descriptions, Reviewers etc... On the UI, the arrangement displaying the Summary, Related Terms, Synonyms, and References has been changed. The Reviewers are shown on the right panel with an option to add or remove existing reviewers.
Profiling data and communicating quality across the organization is core to OpenMetadata. While numerous tools exist, they are often isolated and require users to navigate multiple interfaces. In OpenMetadata, these tests and data profiles are displayed alongside your assets (tables, views) and allow you to get a 360-degree view of your data.
While OpenMetadata allows you to set up and run data quality tests directly from the UI, we understand certain organizations already have their own data quality tool. That’s why we have developed a direct integration between Great Expectations and OpenMetadata. Using our openmetadata-ingestion[great-expectations]
python submodule, you can now add custom actions to your Great Expectations checkpoints file that will automatically ingest your data quality test results into OpenMetadata at the end of your checkpoint file run.
In this release, we are happy to share the addition of ML Model Entities to the UI. This will allow users to describe, and share models and their features as any other data asset. The UI support also includes the ingestion through the UI from MLflow. In future releases, we will add connectors to other popular ML platforms.
This is just the beginning. We want to learn about the use cases from the community and connect with people that want to help us shape the vision and roadmap. Do not hesitate to reach out!
In every release, OpenMetadata has maintained its focus on adding new connectors. In the 0.11 release, five new connectors have been added - Airbyte, Mode, AWS Data Lake, Google Cloud Data Lake, and Apache Pinot.
Published by akash-jain-10 over 2 years ago
0.10.4 is a minor release with following fixes -
#5303
#5468
#5459
#5500
#5543
Published by akash-jain-10 over 2 years ago
0.10.3 is a minor release with following fixes
#5070
#5203
#5224
#5275
Published by akash-jain-10 over 2 years ago
0.10.2 is a minor release with following fixes
#5148
#5256
#5267
#5272
Published by akash-jain-10 over 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.10.0-release...0.10.1-release
Published by akash-jain-10 over 2 years ago
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 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.
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 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.
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.
Support has been added for Azure SSO on Airflow.
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.8.1-release...0.10.0-release
Published by akash-jain-10 over 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.8.1-release...0.9.1-release
Published by akash-jain-10 over 2 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.8.1-release...0.9.0-release
Published by akash-jain-10 over 2 years ago
This is a bug fix release for #2940.
Published by akash-jain-10 over 2 years ago
This is a bug fix release for the #2490.
Published by harshach over 2 years ago
This is a bug fix release for the https://github.com/open-metadata/OpenMetadata/issues/2843
Published by harshach over 2 years ago
This is a bug fix release for the #2843
Published by akash-jain-10 over 2 years ago
Published by harshach almost 3 years ago
Published by harshach almost 3 years ago
##Lineage View Improvements
Published by harshach almost 3 years ago
Published by harshach about 3 years ago
Full Changelog: https://github.com/open-metadata/OpenMetadata/compare/0.4.0-pre...0.5.0