Doc: Lineage Images Updation (#21419)

This commit is contained in:
Rounak Dhillon 2025-05-29 13:50:06 +05:30 committed by GitHub
parent 4d40718ad1
commit cff03f8219
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
14 changed files with 24 additions and 24 deletions

View File

@ -19,10 +19,10 @@ If the database has views, then the view lineage would be generated automaticall
caption="View Lineage through Metadata Ingestion"
/%}
## Lineage Ingestion from UI
Apart from the Metadata ingestion, we can create a workflow that will obtain the query log and table creation information from the underlying database and feed it to OpenMetadata. The Lineage Ingestion will be in charge of obtaining this data. The metadata ingestion will only bring in the View lineage queries, whereas the lineage ingestion workflow will be bring in all those queries that can be used to generate lineage information.
## Lineage Agent from UI
Apart from the Metadata ingestion, we can create a workflow that will obtain the query log and table creation information from the underlying database and feed it to OpenMetadata. The Lineage Agent will be in charge of obtaining this data. The metadata ingestion will only bring in the View lineage queries, whereas the Lineage Agent workflow will be bring in all those queries that can be used to generate lineage information.
### 1. Add a Lineage Ingestion
### 1. Add a Lineage Agent
Navigate to **Settings >> Services >> Databases**. Select the required service
{% image
@ -43,20 +43,20 @@ Navigate to **Settings >> Services >> Databases**. Select the required service
caption="Select the Database"
/%}
Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Lineage Ingestion**.
Go the the **Agents** tab. Click on **Add Agent** and select **Add Lineage Agent**.
{% image
src="/images/v1.7/how-to-guides/lineage/wkf2.png"
alt="Add a Lineage Ingestion"
caption="Add a Lineage Ingestion"
alt="Add a Lineage Agent"
caption="Add a Lineage Agent"
/%}
### 2. Configure the Lineage Ingestion
### 2. Configure the Lineage Agent
Here you can enter the Lineage Ingestion details:
Here you can enter the Lineage Agent details:
{% image
src="/images/v1.7/how-to-guides/lineage/wkf3.png"
alt="Configure the Lineage Ingestion"
caption="Configure the Lineage Ingestion"
alt="Configure the Lineage Agent"
caption="Configure the Lineage Agent"
/%}
### Lineage Options
@ -74,8 +74,8 @@ 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.7/how-to-guides/lineage/wkf4.png"
alt="Schedule and Deploy the Lineage Ingestion"
caption="Schedule and Deploy the Lineage Ingestion"
alt="Schedule and Deploy the Lineage Agent"
caption="Schedule and Deploy the Lineage Agent"
/%}
## Run Lineage Workflow Externally

View File

@ -19,10 +19,10 @@ If the database has views, then the view lineage would be generated automaticall
caption="View Lineage through Metadata Ingestion"
/%}
## Lineage Ingestion from UI
Apart from the Metadata ingestion, we can create a workflow that will obtain the query log and table creation information from the underlying database and feed it to OpenMetadata. The Lineage Ingestion will be in charge of obtaining this data. The metadata ingestion will only bring in the View lineage queries, whereas the lineage ingestion workflow will be bring in all those queries that can be used to generate lineage information.
## Lineage Agent from UI
Apart from the Metadata ingestion, we can create a workflow that will obtain the query log and table creation information from the underlying database and feed it to OpenMetadata. The Lineage Agent will be in charge of obtaining this data. The metadata ingestion will only bring in the View lineage queries, whereas the Lineage Agent workflow will be bring in all those queries that can be used to generate lineage information.
### 1. Add a Lineage Ingestion
### 1. Add a Lineage Agent
Navigate to **Settings >> Services >> Databases**. Select the required service
{% image
@ -43,20 +43,20 @@ Navigate to **Settings >> Services >> Databases**. Select the required service
caption="Select the Database"
/%}
Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Lineage Ingestion**.
Go the the **Ingestions** tab. Click on **Add Ingestion** and select **Add Lineage Agent**.
{% image
src="/images/v1.8/how-to-guides/lineage/wkf2.png"
alt="Add a Lineage Ingestion"
caption="Add a Lineage Ingestion"
alt="Add a Lineage Agent"
caption="Add a Lineage Agent"
/%}
### 2. Configure the Lineage Ingestion
### 2. Configure the Lineage Agent
Here you can enter the Lineage Ingestion details:
Here you can enter the Lineage Agent details:
{% image
src="/images/v1.8/how-to-guides/lineage/wkf3.png"
alt="Configure the Lineage Ingestion"
caption="Configure the Lineage Ingestion"
alt="Configure the Lineage Agent"
caption="Configure the Lineage Agent"
/%}
### Lineage Options
@ -74,8 +74,8 @@ 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.8/how-to-guides/lineage/wkf4.png"
alt="Schedule and Deploy the Lineage Ingestion"
caption="Schedule and Deploy the Lineage Ingestion"
alt="Schedule and Deploy the Lineage Agent"
caption="Schedule and Deploy the Lineage Agent"
/%}
## Run Lineage Workflow Externally

Binary file not shown.

Before

Width:  |  Height:  |  Size: 379 KiB

After

Width:  |  Height:  |  Size: 665 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 1.9 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 990 KiB

After

Width:  |  Height:  |  Size: 742 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 453 KiB

After

Width:  |  Height:  |  Size: 497 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 360 KiB

After

Width:  |  Height:  |  Size: 576 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 432 KiB

After

Width:  |  Height:  |  Size: 536 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 379 KiB

After

Width:  |  Height:  |  Size: 665 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.2 MiB

After

Width:  |  Height:  |  Size: 1.9 MiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 990 KiB

After

Width:  |  Height:  |  Size: 742 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 453 KiB

After

Width:  |  Height:  |  Size: 497 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 360 KiB

After

Width:  |  Height:  |  Size: 576 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 432 KiB

After

Width:  |  Height:  |  Size: 536 KiB