Docs: Adding Data Lineage Workflow Images (#18365)

This commit is contained in:
RounakDhillon 2024-10-31 10:10:03 +05:30 committed by GitHub
parent a9ec754eca
commit 728c321b31
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
16 changed files with 32 additions and 8 deletions

View File

@ -24,13 +24,25 @@ Apart from the Metadata ingestion, we can create a workflow that will obtain the
### 1. Add a Lineage Ingestion
Navigate to **Settings >> Services**. Select the required service
Navigate to **Settings >> Services >> Databases**. Select the required service
{% image
src="/images/v1.5/how-to-guides/lineage/wkf1.png"
alt="Select a Service"
caption="Select a Service"
/%}
{% image
src="/images/v1.5/how-to-guides/lineage/wkf1.1.png"
alt="Click on Databases"
caption="Click on Databases"
/%}
{% image
src="/images/v1.5/how-to-guides/lineage/wkf1.2.png"
alt="Select the Database"
caption="Select the Database"
/%}
Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Lineage Ingestion**.
{% image
src="/images/v1.5/how-to-guides/lineage/wkf2.png"

View File

@ -14,7 +14,7 @@ Once the metadata ingestion runs correctly, and we are able to explore the servi
If the database has views, then the view lineage would be generated automatically, along with the column-level lineage. In such a case, the table type is **View** as shown in the example below.
{% image
src="/images/v1.5/how-to-guides/lineage/view.png"
src="/images/v1.6/how-to-guides/lineage/view.png"
alt="View Lineage through Metadata Ingestion"
caption="View Lineage through Metadata Ingestion"
/%}
@ -24,16 +24,28 @@ Apart from the Metadata ingestion, we can create a workflow that will obtain the
### 1. Add a Lineage Ingestion
Navigate to **Settings >> Services**. Select the required service
Navigate to **Settings >> Services >> Databases**. Select the required service
{% image
src="/images/v1.5/how-to-guides/lineage/wkf1.png"
src="/images/v1.6/how-to-guides/lineage/wkf1.png"
alt="Select a Service"
caption="Select a Service"
/%}
{% image
src="/images/v1.6/how-to-guides/lineage/wkf1.1.png"
alt="Click on Databases"
caption="Click on Databases"
/%}
{% image
src="/images/v1.6/how-to-guides/lineage/wkf1.2.png"
alt="Select the Database"
caption="Select the Database"
/%}
Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Lineage Ingestion**.
{% image
src="/images/v1.5/how-to-guides/lineage/wkf2.png"
src="/images/v1.6/how-to-guides/lineage/wkf2.png"
alt="Add a Lineage Ingestion"
caption="Add a Lineage Ingestion"
/%}
@ -42,7 +54,7 @@ Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Linea
Here you can enter the Lineage Ingestion details:
{% image
src="/images/v1.5/how-to-guides/lineage/wkf3.png"
src="/images/v1.6/how-to-guides/lineage/wkf3.png"
alt="Configure the Lineage Ingestion"
caption="Configure the Lineage Ingestion"
/%}
@ -61,7 +73,7 @@ Here you can enter the Lineage Ingestion details:
After clicking Next, you will be redirected to the Scheduling form. This will be the same as the Metadata Ingestion. Select your desired schedule and click on Deploy to find the lineage pipeline being added to the Service Ingestions.
{% image
src="/images/v1.5/how-to-guides/lineage/wkf4.png"
src="/images/v1.6/how-to-guides/lineage/wkf4.png"
alt="Schedule and Deploy the Lineage Ingestion"
caption="Schedule and Deploy the Lineage Ingestion"
/%}
@ -90,4 +102,4 @@ Lineage can also be added and edited manually in OpenMetadata. Refer for more in
icon="MdArrowForward"
href="/how-to-guides/data-lineage/explore"%}
Explore the rich lineage view in OpenMetadata.
{%/inlineCallout%}
{%/inlineCallout%}

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.7 MiB

After

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 500 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 725 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 948 KiB

After

Width:  |  Height:  |  Size: 519 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 667 KiB

After

Width:  |  Height:  |  Size: 453 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 770 KiB

After

Width:  |  Height:  |  Size: 360 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 639 KiB

After

Width:  |  Height:  |  Size: 432 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.7 MiB

After

Width:  |  Height:  |  Size: 1.2 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 500 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 725 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 948 KiB

After

Width:  |  Height:  |  Size: 519 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 667 KiB

After

Width:  |  Height:  |  Size: 453 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 770 KiB

After

Width:  |  Height:  |  Size: 360 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 639 KiB

After

Width:  |  Height:  |  Size: 432 KiB