This is an automated email from the ASF dual-hosted git repository.
mobuchowski pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new f9f727d3673 Document hook lineage collection limits (#71450)
f9f727d3673 is described below
commit f9f727d3673a6b286357539366190a7813c60a20
Author: Ramit Kataria <[email protected]>
AuthorDate: Wed Aug 12 04:10:25 2026 -0700
Document hook lineage collection limits (#71450)
The lineage page explained how the hook lineage collector works but never
mentioned that collection is bounded, so users hitting the cap had no way to
find out why assets stopped appearing or how to turn collection off.
---
airflow-core/docs/administration-and-deployment/lineage.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/airflow-core/docs/administration-and-deployment/lineage.rst
b/airflow-core/docs/administration-and-deployment/lineage.rst
index a587d5d5e38..857910e5f4c 100644
--- a/airflow-core/docs/administration-and-deployment/lineage.rst
+++ b/airflow-core/docs/administration-and-deployment/lineage.rst
@@ -63,3 +63,12 @@ which is registered in an Airflow plugin.
If no ``HookLineageReader`` is registered within Airflow, a default
``NoOpCollector`` is used instead.
This collector does not create AIP-60 compliant assets or collect lineage
information.
+
+Limiting collected lineage
+--------------------------
+
+A collector keeps at most :ref:`config:lineage__max_assets_per_collector`
input assets and the
+same number of output assets, counted separately, along with
+:ref:`config:lineage__max_extras_per_collector` extra metadata entries.
Entries beyond a limit are
+dropped, so a hook called in a long loop stops contributing lineage once its
limit is reached.
+Setting a limit to ``0`` disables that kind of collection entirely.
