From bb4bbefee6cc7dc291ec5d6b64a7c65ef1e19f41 Mon Sep 17 00:00:00 2001
From: Rounak Dhillon <162090200+RounakDhillon@users.noreply.github.com>
Date: Thu, 7 Aug 2025 16:29:13 +0530
Subject: [PATCH] Docs: Airflow Configuration Note Updation (#22817)

---
 .../pipeline/airflow/configuring-lineage.md        | 11 +++++++++++
 .../pipeline/airflow/configuring-lineage.md        | 14 +++++++++++++-
 .../pipeline/airflow/configuring-lineage.md        | 14 +++++++++++++-
 3 files changed, 37 insertions(+), 2 deletions(-)

diff --git a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/configuring-lineage.md b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/configuring-lineage.md
index 1d6aa869e9e..6b2600d90a4 100644
--- a/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/configuring-lineage.md
+++ b/openmetadata-docs/content/v1.7.x/connectors/pipeline/airflow/configuring-lineage.md
@@ -179,6 +179,17 @@ The `entity` key needs to be informed as follows for each of the entity types:
 - SearchIndex: `searchIndex`
 - MlModel: `mlmodel`
 
+{% note %}
+
+When configuring Airflow lineage without the `openmetadata-ingestion package`, **only table entities** are supported using the simplified format:
+
+```python
+inlets = [{"tables": ["service.db.schema.table"]}]
+```
+- Dashboards, topics, and other non-table entities are not supported in this format.
+- To use those, you must use the full `OMEntity` format, which requires the `openmetadata-ingestion package`.
+
+{% /note %}
 
 ## Configuring Lineage between Tables
 
diff --git a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/configuring-lineage.md b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/configuring-lineage.md
index 1d6aa869e9e..0c766cee1fd 100644
--- a/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/configuring-lineage.md
+++ b/openmetadata-docs/content/v1.8.x/connectors/pipeline/airflow/configuring-lineage.md
@@ -1,5 +1,6 @@
 ---
-title: Configuring DAG Lineage
+title: Configuring DAG Lineage in Airflow | `brandName` Integration
+description: Learn how to configure DAG lineage in Airflow using inlets and outlets. Supports tables, dashboards, pipelines, and more with or without ingestion packages.
 slug: /connectors/pipeline/airflow/configuring-lineage
 ---
 
@@ -179,6 +180,17 @@ The `entity` key needs to be informed as follows for each of the entity types:
 - SearchIndex: `searchIndex`
 - MlModel: `mlmodel`
 
+{% note %}
+
+When configuring Airflow lineage without the `openmetadata-ingestion package`, **only table entities** are supported using the simplified format:
+
+```python
+inlets = [{"tables": ["service.db.schema.table"]}]
+```
+- Dashboards, topics, and other non-table entities are not supported in this format.
+- To use those, you must use the full `OMEntity` format, which requires the `openmetadata-ingestion package`.
+
+{% /note %}
 
 ## Configuring Lineage between Tables
 
diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/configuring-lineage.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/configuring-lineage.md
index 1d6aa869e9e..0c766cee1fd 100644
--- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/configuring-lineage.md
+++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/connectors/pipeline/airflow/configuring-lineage.md
@@ -1,5 +1,6 @@
 ---
-title: Configuring DAG Lineage
+title: Configuring DAG Lineage in Airflow | `brandName` Integration
+description: Learn how to configure DAG lineage in Airflow using inlets and outlets. Supports tables, dashboards, pipelines, and more with or without ingestion packages.
 slug: /connectors/pipeline/airflow/configuring-lineage
 ---
 
@@ -179,6 +180,17 @@ The `entity` key needs to be informed as follows for each of the entity types:
 - SearchIndex: `searchIndex`
 - MlModel: `mlmodel`
 
+{% note %}
+
+When configuring Airflow lineage without the `openmetadata-ingestion package`, **only table entities** are supported using the simplified format:
+
+```python
+inlets = [{"tables": ["service.db.schema.table"]}]
+```
+- Dashboards, topics, and other non-table entities are not supported in this format.
+- To use those, you must use the full `OMEntity` format, which requires the `openmetadata-ingestion package`.
+
+{% /note %}
 
 ## Configuring Lineage between Tables