Visitar URL original
New example along storyline: Turbine report · Issue #52481 · apache/airflow · GitHub
Skip to content

New example along storyline: Turbine report #52481

Open

Description

@jscheffl

Description

As described in https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish

A new Dag is implemented along the described storyline for "Turbine report"

This includes:

  • New Dag is added in Taskflow as well as classic implementation
  • Dag is according to checklist
  • Previous examples that are content-wise replaced are deleted to incrementally clean-up
  • Airflow documentation is adjusted to point to new examples are replaced
  • General example storyline overview is adjusted and the functioning of the new example is described

Use case/motivation

Airflow Examples have been grown in number and focus over the past years. They purpose multiple things:

Serve as tutorials to learn Airflow DAG implementation
Serve with code snippets for documentation
Serve for testing the setup
(some) service for CI integration testing

Some example DAGs are in a good quality, some are not following best practices. Current examples do not follow a structure.

There are example DAGs contained in the Airflow core (currently pushed to standard provider/example_dags) as well as there are more examples in other providers. But examples from other providers are lot loaded automatically.

So in the Airflow 3 Dev Calls there was a demand named to clean-up and optimize example DAGs.

Related issues

#52476 is made before and might be adjusted

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. added this to the Airflow 3.1.0 milestone on Jun 29, 2025
  2. added theissue type on Jun 29, 2025
  3. amoghrajesh commented on Aug 25, 2025

    @amoghrajesh
    Contributor

    Per Slack thread, targeting “example DAGs” won’t be possible in 3.1, so we’re moving this to Airflow 3.1+

  4. andreahlert commented on May 2, 2026

    @andreahlert
    Contributor

    revisiting #53352 since the epic is moving again. one thing I want to sanity check before picking it up: the implementation in that draft is actually a dynamic stakeholder dag generator, which feels closer to #52478 than to a turbine report.

    does the original "Turbine report" issue still mean what it did back in june, or did the scope shift after the 3.1+ move? want to make sure I rebuild the right thing if we go forward with it.

    @jscheffl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions