annotating-task-lineage

This skill guides you through adding manual lineage annotations to Airflow tasks using inlets and outlets . Reference: See the OpenLineage provider developer guide for the latest supported operators and patterns. Lineage annotations defined with inlets and outlets are visualized in Astro's enhanced Lineage tab , which provides cross-DAG and cross-deployment lineage views. This means your annotations are immediately visible in the Astro UI, giving you a unified view of data flow across your entire Astro organization. Note: Inlets/outlets are the lowest-priority fallback. If an OpenLineage extractor or method exists for the operator, it takes precedence. Use this approach for operators without extractors. You can use OpenLineage Dataset objects or Airflow Assets for inlets and outlets: Tasks often read from multiple sources and write to multiple destinations: When building custom operators, you have two options: This is the preferred approach as it gives you full control over lineage extraction: For simpler cases, set lineage within the execute method (non-deferrable operators only): Use the OpenLineage dataset naming helpers to ensure consistent naming across platforms: Note: Always use the naming helpers instead of constructing namespaces manually.