mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-12-28 07:58:31 +00:00
doc : Updated what's new modal content for 0.13.0 (#8954)
* doc : Updated what's new modal content for `0.13.0` * Add data profiler feature info
This commit is contained in:
parent
5afc7aaf81
commit
37f8fd36f8
@ -552,7 +552,36 @@ export const WHATS_NEW = [
|
||||
id: 10,
|
||||
version: 'v0.13.0',
|
||||
description: 'Released on 22 November 2022.',
|
||||
features: [],
|
||||
features: [
|
||||
{
|
||||
title: 'Data Insights and KPIs',
|
||||
description:
|
||||
'Data Insights has been introduced that transforms the passive approach to data to a collaborative project towards improved data culture. Data Insights aims to provide a single pane view of all the key metrics to best reflect the state of your data. Admins can define the Key Performance Indicators (KPIs) and set goals within OpenMetadata to work towards better documentation, ownership, and tiering.',
|
||||
isImage: false,
|
||||
path: 'https://www.youtube.com/embed/pCR0y5jyHCA',
|
||||
},
|
||||
{
|
||||
title: 'Lineage Traceability',
|
||||
description:
|
||||
'The lineage UI has been transformed to enhance user experience. Users can get a holistic view of an entity from the Lineage tab. When an entity is selected, the UI displays end-to-end lineage traceability for the table and column levels. Just search for an entity and expand the graph to unfold lineage. It’ll display the upstream and downstream for each node.',
|
||||
isImage: false,
|
||||
path: 'https://www.youtube.com/embed/j_elWRYSelU',
|
||||
},
|
||||
{
|
||||
title: 'Advanced Search',
|
||||
description:
|
||||
'An advanced search feature has been introduced in the 0.13.0 release, which helps users discover assets quickly with a Syntax Editor based on And/Or conditions.',
|
||||
isImage: false,
|
||||
path: 'https://www.youtube.com/embed/4EYUdBm5-K4',
|
||||
},
|
||||
{
|
||||
title: 'Data Lake Profiler',
|
||||
description:
|
||||
'With the OpenMetadata UI, users can now create and deploy profiling workflows for the Data Lake connector, which supports AWS S3 and GCS.',
|
||||
isImage: false,
|
||||
path: 'https://www.youtube.com/embed/KJ0vHGRIcG4',
|
||||
},
|
||||
],
|
||||
changeLogs: {
|
||||
'Data Insights and KPIs': `- Provides a single pane view of all the key data metrics.
|
||||
- Analytics are provided based on the metadata metrics, the entities created, the types of entities, and the data evolution over a period of time.
|
||||
@ -564,28 +593,12 @@ export const WHATS_NEW = [
|
||||
- Admins can view the **aggregated user activity** and get insights into user engagement and user growth.
|
||||
- Admins can check for Daily active users and know how OpenMetadata is being used.
|
||||
- The **Data Insights Report** is emailed weekly to assess team performance.`,
|
||||
Glossary: `- Introduced the functionality to **bulk upload glossary terms**.
|
||||
- Upload a CSV with thousands of terms in one go.
|
||||
- Define the **Owners and Reviewers** during bulk upload.
|
||||
- Owners and Reviewers will be propagated to every glossary term.
|
||||
- Users can **Preview** before uploading to ensure that everything looks right.
|
||||
- Support a **Review Workflow** for new term suggestions.
|
||||
- Suggested terms will be saved as Draft terms.
|
||||
- Admins can review and approve these draft terms.
|
||||
- Once approved, these terms can be used for tagging and searching.
|
||||
- A glossary term can be moved to a different hierarchy within a glossary or across a glossary.
|
||||
- While moving a term, even the child terms will be moved along with the parent term.`,
|
||||
|
||||
Lineage: `- The UI displays end-to-end **lineage** **traceability** for the table and column levels.
|
||||
- Users can search for an entity and expand the graph to unfold lineage.
|
||||
- Displays the upstream and downstream for each node.
|
||||
- Lineage Tab UI supports two-finger scrolling to zoom in or zoom out.
|
||||
`,
|
||||
'Data Quality': `- We support **profiling** for **Data lakes** like Amazon S3.
|
||||
- **Freshness metric** has been introduced based on the partition key.
|
||||
- Data freshness is defined by how often the table is being updated and the number of rows being updated.
|
||||
- All this is displayed within the profiler.
|
||||
- Users can create alerts for the same.`,
|
||||
'Data Quality': `- We support **profiling** for **Data lakes** like Amazon S3.`,
|
||||
Security: `- **LDAP SSO** has been introduced.
|
||||
- In the 0.12.1 release, support was added for **basic authentication** to sign up using a Username/Password.
|
||||
- Created multiple **bots to serve different scenarios**. For example, Ingestion Bot, Lineage Bot, Data Quality and Profiler Bot.
|
||||
@ -598,7 +611,6 @@ export const WHATS_NEW = [
|
||||
- Ingestion framework has been improved.
|
||||
- Adding a [**custom service type**](https://docs.open-metadata.org/connectors/custom-connectors) supported from the 0.12.1 release.`,
|
||||
'Messaging Service Schemas': `- We now parse **Avro** and **Protobuf Schemas** to extract the fields from **Kafka** and **Redpanda** Messaging services. Previously, the schemas were taken as one payload and just published to OpenMetadata.
|
||||
- A **nested schema** view of the Topic entities is displayed.
|
||||
- Users can **document** each of these fields within a schema by adding description and tags.
|
||||
- Users can **search** based on the fields in the Schema of a Topic.`,
|
||||
'Other Changes': `- **Soft deleted entities** can be restored. Currently, only the ML Models are not supported.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user