From 95c56390c0258286e062e786255dd1e8846b289e Mon Sep 17 00:00:00 2001 From: Mayur Singal <39544459+ulixius9@users.noreply.github.com> Date: Mon, 9 Dec 2024 16:10:50 +0530 Subject: [PATCH] MINOR: Add Lineage breaking changes (#18970) --- .../deployment/upgrade/upgrade-prerequisites.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/openmetadata-docs/content/partials/v1.6/deployment/upgrade/upgrade-prerequisites.md b/openmetadata-docs/content/partials/v1.6/deployment/upgrade/upgrade-prerequisites.md index 48f8a1468f4..3004c74156d 100644 --- a/openmetadata-docs/content/partials/v1.6/deployment/upgrade/upgrade-prerequisites.md +++ b/openmetadata-docs/content/partials/v1.6/deployment/upgrade/upgrade-prerequisites.md @@ -98,6 +98,12 @@ workflow as successful. However, any errors when sending the information to Open Now, we're changing this behavior to consider the success rate of all the steps involved in the workflow. The UI will then show more `Partial Success` statuses rather than `Failed`, properly reflecting the real state of the workflow. +# Database Metadata & Lineage Workflow + +With 1.6 Release we are moving the `View Lineage` & `Stored Procedure Lineage` computation from metadata workflow to lineage workflow. + +This means that we are removing the `overrideViewLineage` property from the `DatabaseServiceMetadataPipeline` schema which will be moved to the `DatabaseServiceQueryLineagePipeline` schema. + ### Profiler & Auto Classification Workflow We are creating a new `Auto Classification` workflow that will take care of managing the sample data and PII classification, @@ -150,4 +156,13 @@ implementation example. ### Fivetran -The filtering of Fivetran pipelines now supports using their names instead of IDs. This change may affect existing configurations that rely on pipeline IDs for filtering. \ No newline at end of file +The filtering of Fivetran pipelines now supports using their names instead of IDs. This change may affect existing configurations that rely on pipeline IDs for filtering. + +### DBT Cloud Pipeline Service + +We are removing the field `jobId` which we required to ingest dbt metadata from a specific job, instead of this we added a new field called `jobIds` which will accept multiple job ids to ingest metadata from multiple jobs. + +### MicroStrategy + +The `serviceType` for MicroStrategy connector is renamed from `Mstr` to `MicroStrategy`. +