doc_id stringlengths 11 42 | source_type stringclasses 5
values | source_url stringlengths 32 176 | license stringclasses 8
values | title stringlengths 3 654 | content stringlengths 439 232k | project stringclasses 35
values | tags listlengths 2 31 | word_count int32 71 33.5k | lang stringclasses 1
value | quality_score float64 0.35 0.9 | scraped_at timestamp[us, tz=UTC]date 2026-09-21 04:26:58 2026-09-21 12:13:36 |
|---|---|---|---|---|---|---|---|---|---|---|---|
aip-0065-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816335 | Apache-2.0 | AIP-65: Improve DAG history in UI — Motivation | Title: AIP-65: Improve DAG history in UI — Motivation
Proposal: AIP-65 | Project: airflow | State: unknown
This AIP is part of AIP-63, which aims to add DAG Versioning to Airflow.
## Motivation
DAGs can change over time as business needs evolve. A key challenge faced by Airflow users today is understanding how a DAG... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:65",
"proposal_state:unknown",
"chunk:0"
] | 252 | en | 0.45 | 2026-09-21T12:13:31.486994Z |
aip-0065-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816335 | Apache-2.0 | AIP-65: Improve DAG history in UI — Requirements | Title: AIP-65: Improve DAG history in UI — Requirements
Proposal: AIP-65 | Project: airflow | State: unknown
## Requirements
For every instantiation of a task run (i.e a task instance run), we will show the following information in a consolidated place:
- The DAG structure at the time of the task instance run
- The ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:65",
"proposal_state:unknown",
"chunk:1"
] | 139 | en | 0.35 | 2026-09-21T12:13:31.486999Z |
aip-0065-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816335 | Apache-2.0 | AIP-65: Improve DAG history in UI — Scenarios | Title: AIP-65: Improve DAG history in UI — Scenarios
Proposal: AIP-65 | Project: airflow | State: unknown
## Scenarios
We will consider 4 different scenarios (in increasing order of complexity):
- DAG changes between two DAG runs
- DAG changes in between two Task Instances in the same DAG run
- DAG changes in betwee... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:65",
"proposal_state:unknown",
"chunk:2"
] | 1,428 | en | 0.55 | 2026-09-21T12:13:31.487002Z |
aip-0065-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816335 | Apache-2.0 | AIP-65: Improve DAG history in UI — Out of scope | Title: AIP-65: Improve DAG history in UI — Out of scope
Proposal: AIP-65 | Project: airflow | State: unknown
## Out of scope
Some things will be out of scope in this AIP.
The DAG Dependencies page will continue to show the relationships between the latest version of the DAGs, with no way to see past relationships.
... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:65",
"proposal_state:unknown",
"chunk:3"
] | 114 | en | 0.35 | 2026-09-21T12:13:31.487006Z |
aip-0065-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816335 | Apache-2.0 | AIP-65: Improve DAG history in UI — Backend Changes | Title: AIP-65: Improve DAG history in UI — Backend Changes
Proposal: AIP-65 | Project: airflow | State: unknown
## Backend Changes
### Determining DAG version
To calculate the DAG version, we will simply hash the serialized DAG json. This is easy for us to calculate and already covers the things in the DAG used by t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:65",
"proposal_state:unknown",
"chunk:4"
] | 250 | en | 0.475 | 2026-09-21T12:13:31.487009Z |
aip-0066-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816356 | Apache-2.0 | AIP-66: DAG Bundles & Parsing — Motivation | Title: AIP-66: DAG Bundles & Parsing — Motivation
Proposal: AIP-66 | Project: airflow | State: unknown
This AIP is part of AIP-63, which aims to add DAG Versioning to Airflow.
This AIP supersedes AIP-5 and AIP-20.
## Motivation
Today, Airflow will always execute tasks using the latest DAG code. While in some cases ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:66",
"proposal_state:unknown",
"chunk:0"
] | 223 | en | 0.45 | 2026-09-21T12:13:30.066528Z |
aip-0066-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816356 | Apache-2.0 | AIP-66: DAG Bundles & Parsing — DAG Bundles | Title: AIP-66: DAG Bundles & Parsing — DAG Bundles
Proposal: AIP-66 | Project: airflow | State: unknown
## DAG Bundles
Airflow will support one or more DAG Bundles (a collection of DAGs and other files, like today's DAG folder). They will support versioning, which allows Airflow to control the version of the DAG code... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:66",
"proposal_state:unknown",
"chunk:1"
] | 734 | en | 0.45 | 2026-09-21T12:13:30.066533Z |
aip-0066-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816356 | Apache-2.0 | AIP-66: DAG Bundles & Parsing — Parsing | Title: AIP-66: DAG Bundles & Parsing — Parsing
Proposal: AIP-66 | Project: airflow | State: unknown
## Parsing
Instead of constantly trying to parse DAG files, we will add support for a manifest file in DAG Bundles. This allows Airflow to support more flexible parsing rules, which will allow users to tell us things l... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:66",
"proposal_state:unknown",
"chunk:2"
] | 260 | en | 0.55 | 2026-09-21T12:13:30.066536Z |
aip-0066-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816356 | Apache-2.0 | AIP-66: DAG Bundles & Parsing — Scheduler | Title: AIP-66: DAG Bundles & Parsing — Scheduler
Proposal: AIP-66 | Project: airflow | State: unknown
## Scheduler
The scheduler, when creating new DAG runs, will always use the latest DAG version.
While scheduling tasks, the scheduler will specify the DAG bundle version when sending the task to the executor, so tha... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:66",
"proposal_state:unknown",
"chunk:3"
] | 151 | en | 0.35 | 2026-09-21T12:13:30.066539Z |
aip-0066-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816356 | Apache-2.0 | AIP-66: DAG Bundles & Parsing — Packaging (Where do DAG Bundle Backends live?) | Title: AIP-66: DAG Bundles & Parsing — Packaging (Where do DAG Bundle Backends live?)
Proposal: AIP-66 | Project: airflow | State: unknown
## Packaging (Where do DAG Bundle Backends live?)
The packaging decisions (e.g. where will the out-of-the-box DAG bundle backends live) will be deferred until we have a better und... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:66",
"proposal_state:unknown",
"chunk:4"
] | 161 | en | 0.35 | 2026-09-21T12:13:30.066542Z |
aip-0067-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Summary | Title: AIP-67: Multi-team deployment of Airflow components — Summary
Proposal: AIP-67 | Project: airflow | State: unknown
## Summary
The multi-team feature described here allows to have a single deployment of Airflow for several/multiple teams that will be isolated from each other in terms of:
- access to team-speci... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:0"
] | 294 | en | 0.45 | 2026-09-21T12:13:30.127094Z |
aip-0067-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Motivation | Title: AIP-67: Multi-team deployment of Airflow components — Motivation
Proposal: AIP-67 | Project: airflow | State: unknown
## Motivation
The main motivation is the need for the users of Airflow to have a single deployment of Airflow, where separate teams in the company structure have access to only a subset of reso... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:1"
] | 203 | en | 0.45 | 2026-09-21T12:13:30.127103Z |
aip-0067-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — High level goal summary | Title: AIP-67: Multi-team deployment of Airflow components — High level goal summary
Proposal: AIP-67 | Project: airflow | State: unknown
## High level goal summary
There was a lot of debate on what **really** are the goals of the proposal and there are - of course - varying opinions on how it fits but as a "north st... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:2"
] | 132 | en | 0.35 | 2026-09-21T12:13:30.127107Z |
aip-0067-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Wording/Phrasing | Title: AIP-67: Multi-team deployment of Airflow components — Wording/Phrasing
Proposal: AIP-67 | Project: airflow | State: unknown
## Wording/Phrasing
Note, that this is not a formal specification, but where emphasised by capital letters, The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:3"
] | 503 | en | 0.45 | 2026-09-21T12:13:30.127110Z |
aip-0067-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Differences of the multi-team proposal vs. current Airflow multi-tenant options | Title: AIP-67: Multi-team deployment of Airflow components — Differences of the multi-team proposal vs. current Airflow multi-tenant options
Proposal: AIP-67 | Project: airflow | State: unknown
## Differences of the multi-team proposal vs. current Airflow multi-tenant options
How exactly the current proposal is diffe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:4"
] | 837 | en | 0.45 | 2026-09-21T12:13:30.127113Z |
aip-0067-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Design Goals | Title: AIP-67: Multi-team deployment of Airflow components — Design Goals
Proposal: AIP-67 | Project: airflow | State: unknown
## Design Goals
### Structural/architectural changes
The goal of the implementation approach proposed is to minimize structural and architectural changes in Airflow to introduce multi-team, ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:5"
] | 1,040 | en | 0.45 | 2026-09-21T12:13:30.127117Z |
aip-0067-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Design Non Goals | Title: AIP-67: Multi-team deployment of Airflow components — Design Non Goals
Proposal: AIP-67 | Project: airflow | State: unknown
## Design Non Goals
It's also important to explain the non-goals of this proposal. This aims to help to get more understanding of what the proposal really means for the users of Airflow a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:6"
] | 649 | en | 0.475 | 2026-09-21T12:13:30.127120Z |
aip-0067-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Architecture | Title: AIP-67: Multi-team deployment of Airflow components — Architecture
Proposal: AIP-67 | Project: airflow | State: unknown
## Architecture
The Multi team Airflow extends "Sepearate DAG processing" architecture described in the Overall Airflow Architecture.
**Current "Separate DAG processing" architecture overvie... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:7"
] | 349 | en | 0.45 | 2026-09-21T12:13:30.127123Z |
aip-0067-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Executor support | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Executor support
Proposal: AIP-67 | Project: airflow | State: unknown
### Executor support
The implementation utilizes AIP-61 (Hybrid Execution) support where each team can have their own set of executors defined (with separate con... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:9"
] | 126 | en | 0.35 | 2026-09-21T12:13:30.127129Z |
aip-0067-10 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Changes in configuration | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Changes in configuration
Proposal: AIP-67 | Project: airflow | State: unknown
### Changes in configuration
Multi-team of scheduler and webserver is controlled by a "core/multi-team" bool flag (default False). Since the access to Co... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:10"
] | 587 | en | 0.55 | 2026-09-21T12:13:30.127134Z |
aip-0067-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Changes in the metadata database | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Changes in the metadata database
Proposal: AIP-67 | Project: airflow | State: unknown
### Changes in the metadata database
Changes to the database are much smaller than in the previoous version of this AIP and they avoid "ripple ef... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:11"
] | 193 | en | 0.35 | 2026-09-21T12:13:30.127137Z |
aip-0067-14 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Roles of Deployment managers | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Roles of Deployment managers
Proposal: AIP-67 | Project: airflow | State: unknown
### Roles of Deployment managers
There are two kinds of Deployment Managers in the multi-team Airflow Architecture: Organisation Deployment Managers ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:14"
] | 873 | en | 0.45 | 2026-09-21T12:13:30.127148Z |
aip-0067-15 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Why is it needed? | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Why is it needed?
Proposal: AIP-67 | Project: airflow | State: unknown
### Why is it needed?
The idea of multi-tenancy has been floating in the community for a long itme, however it was ill-defined. It was not clear who would be th... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:15"
] | 214 | en | 0.45 | 2026-09-21T12:13:30.127152Z |
aip-0067-16 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Which users are affected by the change? | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › Which users are affected by the change?
Proposal: AIP-67 | Project: airflow | State: unknown
### Which users are affected by the change?
- The change does not affect users who do not enable multi-team mode. There will be no databas... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:16"
] | 123 | en | 0.35 | 2026-09-21T12:13:30.127154Z |
aip-0067-17 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=294816378 | Apache-2.0 | AIP-67: Multi-team deployment of Airflow components — Implementation proposal › What is excluded from the scope? | Title: AIP-67: Multi-team deployment of Airflow components — Implementation proposal › What is excluded from the scope?
Proposal: AIP-67 | Project: airflow | State: unknown
### What is excluded from the scope?
- Sharing broker/backend for celery executors between teams. This MAY be covered by future AIPs
- Implementa... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:67",
"proposal_state:unknown",
"chunk:17"
] | 454 | en | 0.45 | 2026-09-21T12:13:30.127159Z |
aip-0068-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795914 | Apache-2.0 | AIP-68: Extended Plugin Interface for React Views — Motivation | Title: AIP-68: Extended Plugin Interface for React Views — Motivation
Proposal: AIP-68 | Project: airflow | State: unknown
## Motivation
After the completion of AIP-79 Remove Flask App Builder we need to explore new ways to build UI plugins. Out-of-the-box, custom plugin views and menu items will no longer be support... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:68",
"proposal_state:unknown",
"chunk:0"
] | 232 | en | 0.45 | 2026-09-21T12:13:30.019254Z |
aip-0068-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795914 | Apache-2.0 | AIP-68: Extended Plugin Interface for React Views — Considerations | Title: AIP-68: Extended Plugin Interface for React Views — Considerations
Proposal: AIP-68 | Project: airflow | State: unknown
## Considerations
General knowledge of the UI and state of development is known by the AIP authors. From this perspective the following options have been considered as options to make a busin... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:68",
"proposal_state:unknown",
"chunk:1"
] | 1,473 | en | 0.45 | 2026-09-21T12:13:30.019260Z |
aip-0069-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Motivation | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Motivation
Proposal: AIP-69 | Project: airflow | State: unknown
## Motivation
The world is moving to cloud! No... see a lot is still running on-prem! Oh, we need to be hybrid. Damn we have actually a distributed system. We want it in the cloud but have th... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:0"
] | 321 | en | 0.425 | 2026-09-21T12:13:32.834422Z |
aip-0069-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations
Proposal: AIP-69 | Project: airflow | State: unknown
## Considerations
To implement the capability for a distributed orchestration crossing network boundaries the following options were considered:
- CeleryExecutor over a VPN or other tunn... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:1"
] | 508 | en | 0.475 | 2026-09-21T12:13:32.834428Z |
aip-0069-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What change do you propose to make? | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What change do you propose to make?
Proposal: AIP-69 | Project: airflow | State: unknown
### What change do you propose to make?
It is proposed to implement an Edge Executor as additional executor option for Airflow in order to distribute... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:2"
] | 1,525 | en | 0.525 | 2026-09-21T12:13:32.834433Z |
aip-0069-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What change do you propose to make? | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What change do you propose to make?
Proposal: AIP-69 | Project: airflow | State: unknown
Edge Worker Authentication | Based on User/Pasword on API | JWT or ID Token | ||
Support / Documentation for automated rollout (e.g. Ansible, Systemd... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:3"
] | 424 | en | 0.425 | 2026-09-21T12:13:32.834437Z |
aip-0069-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What problem does it solve? | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › What problem does it solve?
Proposal: AIP-69 | Project: airflow | State: unknown
### What problem does it solve?
- If a worker in current Airflow is to be maintained outside of the core setup it is hard to (manually) integrate e.g. via Ce... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:4"
] | 298 | en | 0.425 | 2026-09-21T12:13:32.834440Z |
aip-0069-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › Why is it needed? | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › Why is it needed?
Proposal: AIP-69 | Project: airflow | State: unknown
### Why is it needed?
It is hard with Airflow (e.g. Celery) to deploy and host a distributed worker system in a different security perimeter. Only workaround in most c... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:5"
] | 114 | en | 0.35 | 2026-09-21T12:13:32.834443Z |
aip-0069-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=301795932 | Apache-2.0 | AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › Other considerations? | Title: AIP-69: Edge Executor (Initial Name: Remote Executor) — Considerations › Other considerations?
Proposal: AIP-69 | Project: airflow | State: unknown
### Other considerations?
As there is a parallel discussion about Airflow 3 ongoing - This AIP might influence design towards Airflow 3 plannings. The target is no... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:69",
"proposal_state:unknown",
"chunk:7"
] | 242 | en | 0.425 | 2026-09-21T12:13:32.834449Z |
aip-0070-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=303794967 | Apache-2.0 | AIP-70: Make Use of Asynchronous Programming in Core Components — Why is it needed? | Title: AIP-70: Make Use of Asynchronous Programming in Core Components — Why is it needed?
Proposal: AIP-70 | Project: airflow | State: unknown
## Why is it needed?
Airflow's execution model currently relies heavily on synchronous blocking calls that serialize I/O operations, resulting in inefficient CPU utilization,... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:70",
"proposal_state:unknown",
"chunk:2"
] | 164 | en | 0.35 | 2026-09-21T12:13:29.943730Z |
aip-0070-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=303794967 | Apache-2.0 | AIP-70: Make Use of Asynchronous Programming in Core Components — Are there any downsides to this change? | Title: AIP-70: Make Use of Asynchronous Programming in Core Components — Are there any downsides to this change?
Proposal: AIP-70 | Project: airflow | State: unknown
## Are there any downsides to this change?
**Increased complexity:**Introducing asynchronous code paths can make debugging, logging, tracing, and testin... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:70",
"proposal_state:unknown",
"chunk:3"
] | 133 | en | 0.35 | 2026-09-21T12:13:29.943734Z |
aip-0071-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153103 | Apache-2.0 | AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Abstract | Title: AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Abstract
Proposal: AIP-71 | Project: airflow | State: unknown
## Abstract
This proposal aims to enhance Apache Airflow's DAG loading mechanism to support reading DAGs from ephemeral storage, superseding AIP-5 Remote DAG Fetcher. The objectiv... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:71",
"proposal_state:unknown",
"chunk:0"
] | 118 | en | 0.35 | 2026-09-21T12:13:34.159876Z |
aip-0071-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153103 | Apache-2.0 | AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Motivation | Title: AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Motivation
Proposal: AIP-71 | Project: airflow | State: unknown
## Motivation
Currently, Airflow's DAG loading mechanism is tightly coupled with the local filesystem, limiting its flexibility and scalability. As organizations increasingly ad... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:71",
"proposal_state:unknown",
"chunk:1"
] | 113 | en | 0.35 | 2026-09-21T12:13:34.159882Z |
aip-0071-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153103 | Apache-2.0 | AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Proposal | Title: AIP-71: Generalizing DAG Loader and Processor for Ephemeral Storage — Proposal
Proposal: AIP-71 | Project: airflow | State: unknown
## Proposal
### Goals
- Generalize the DAG loader and processor to use `pathlib.Path` for file operations.
- Implement a custom module loader to support `ObjectStoragePath` and o... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:71",
"proposal_state:unknown",
"chunk:2"
] | 425 | en | 0.45 | 2026-09-21T12:13:34.159886Z |
aip-0072-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626182 | Apache-2.0 | AIP-72: Task Execution Interface aka Task SDK — Motivation | Title: AIP-72: Task Execution Interface aka Task SDK — Motivation
Proposal: AIP-72 | Project: airflow | State: unknown
## Motivation
Historically, Airflow's task execution context has been oriented around local execution within a relatively trusted networking cluster.
This includes:
- the interaction between the Ex... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:72",
"proposal_state:unknown",
"chunk:0"
] | 565 | en | 0.45 | 2026-09-21T12:13:28.987063Z |
aip-0072-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626182 | Apache-2.0 | AIP-72: Task Execution Interface aka Task SDK — Considerations › What change do you propose to make? | Title: AIP-72: Task Execution Interface aka Task SDK — Considerations › What change do you propose to make?
Proposal: AIP-72 | Project: airflow | State: unknown
### What change do you propose to make?
At a high level we propose the following changes:
- To completely disable direct database access from all tasks and ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:72",
"proposal_state:unknown",
"chunk:1"
] | 1,509 | en | 0.55 | 2026-09-21T12:13:28.987069Z |
aip-0072-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626182 | Apache-2.0 | AIP-72: Task Execution Interface aka Task SDK — Considerations › What change do you propose to make? | Title: AIP-72: Task Execution Interface aka Task SDK — Considerations › What change do you propose to make?
Proposal: AIP-72 | Project: airflow | State: unknown
Parsing DAG files involves running user code so this activity needs to have the same security properties as executing a task. To enable this the following cha... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:72",
"proposal_state:unknown",
"chunk:2"
] | 613 | en | 0.45 | 2026-09-21T12:13:28.987073Z |
aip-0072-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626182 | Apache-2.0 | AIP-72: Task Execution Interface aka Task SDK — Considerations › Other considerations? | Title: AIP-72: Task Execution Interface aka Task SDK — Considerations › Other considerations?
Proposal: AIP-72 | Project: airflow | State: unknown
### Other considerations?
Having a different SDK that operators and triggers need to import is quite a sizeable change, but it is the only way to truly decouple provider c... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:72",
"proposal_state:unknown",
"chunk:3"
] | 157 | en | 0.35 | 2026-09-21T12:13:28.987076Z |
aip-0073-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626828 | Apache-2.0 | AIP-73: Expanded Data Awareness — Motivation | Title: AIP-73: Expanded Data Awareness — Motivation
Proposal: AIP-73 | Project: airflow | State: unknown
## Motivation
Airflow has become the standard for orchestrating complex data workflows. However, it operates with limited visibility into the actual data it processes or produces. While it understands task executi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:73",
"proposal_state:unknown",
"chunk:0"
] | 135 | en | 0.375 | 2026-09-21T12:13:27.488461Z |
aip-0073-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626828 | Apache-2.0 | AIP-73: Expanded Data Awareness — Rationale | Title: AIP-73: Expanded Data Awareness — Rationale
Proposal: AIP-73 | Project: airflow | State: unknown
## Rationale
In the context of data engineering, assets are the data entities that move through pipelines, undergo transformations, and ultimately drive business insights and power data products. Although data engi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:73",
"proposal_state:unknown",
"chunk:1"
] | 496 | en | 0.625 | 2026-09-21T12:13:27.488466Z |
aip-0073-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626828 | Apache-2.0 | AIP-73: Expanded Data Awareness — Proposed Changes | Title: AIP-73: Expanded Data Awareness — Proposed Changes
Proposal: AIP-73 | Project: airflow | State: unknown
## Proposed Changes
Due to the scope of proposed changes, we will be using the current AIP as an umbrella AIP and split the proposal into 4 sub-AIPs:
**AIP-74 Introducing Data Assets:**This proposal focuses... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:73",
"proposal_state:unknown",
"chunk:2"
] | 251 | en | 0.5 | 2026-09-21T12:13:27.488470Z |
aip-0073-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626828 | Apache-2.0 | AIP-73: Expanded Data Awareness — Future Works | Title: AIP-73: Expanded Data Awareness — Future Works
Proposal: AIP-73 | Project: airflow | State: unknown
## Future Works
As we continue to enhance Airflow's data awareness capabilities, there are several key areas of improvement that we plan to address in future iterations. These enhancements aim to further optimiz... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:73",
"proposal_state:unknown",
"chunk:3"
] | 343 | en | 0.525 | 2026-09-21T12:13:27.488473Z |
aip-0074-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627073 | Apache-2.0 | AIP-74: Introducing Data Assets — Rationale | Title: AIP-74: Introducing Data Assets — Rationale
Proposal: AIP-74 | Project: airflow | State: unknown
This AIP is part of AIP-73, which aims to expand data awareness within Airflow.
## Rationale
A data asset is, fundamentally, a collection of logically related data. This can be one of (but not limited to):
- A ta... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:74",
"proposal_state:unknown",
"chunk:0"
] | 264 | en | 0.6 | 2026-09-21T12:13:27.496837Z |
aip-0074-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627073 | Apache-2.0 | AIP-74: Introducing Data Assets — Proposed Changes | Title: AIP-74: Introducing Data Assets — Proposed Changes
Proposal: AIP-74 | Project: airflow | State: unknown
## Proposed Changes
### Rename Datasets to Assets
Taking inspiration from other tooling like Great Expectations, Atlan and Dagster, we propose to rename *Datasets* to *Assets*, and potentially introduce sub... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:74",
"proposal_state:unknown",
"chunk:1"
] | 719 | en | 0.625 | 2026-09-21T12:13:27.496843Z |
aip-0074-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627073 | Apache-2.0 | AIP-74: Introducing Data Assets — Future Work | Title: AIP-74: Introducing Data Assets — Future Work
Proposal: AIP-74 | Project: airflow | State: unknown
## Future Work
### Asset Annotations
An additional benefit of using subclasses is we can add additional parameters to a specific asset. The parameters can provide annotations with a structure common to the asset... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:74",
"proposal_state:unknown",
"chunk:4"
] | 182 | en | 0.525 | 2026-09-21T12:13:27.496852Z |
aip-0075-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — Proposed Changes | Title: AIP-75: New Asset-Centric Syntax — Proposed Changes
Proposal: AIP-75 | Project: airflow | State: unknown
This AIP is part of AIP-73, which aims to expand data awareness within Airflow.
## Proposed Changes
We propose extending the taskflow API to include asset-centric primitives to improve the interface for im... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:0"
] | 968 | en | 0.675 | 2026-09-21T12:13:31.465509Z |
aip-0075-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — User Presentation Considerations | Title: AIP-75: New Asset-Centric Syntax — User Presentation Considerations
Proposal: AIP-75 | Project: airflow | State: unknown
## User Presentation Considerations
Since an `@asset` declaration still creates a regular DAG and a regular asset, it should be displayed appropriately without additional work in the web UI,... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:1"
] | 196 | en | 0.35 | 2026-09-21T12:13:31.465515Z |
aip-0075-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — Effects on Terminology | Title: AIP-75: New Asset-Centric Syntax — Effects on Terminology
Proposal: AIP-75 | Project: airflow | State: unknown
## Effects on Terminology
While the `@asset` syntax still creates a DAG behind the scenes, a user using the decorator would no longer be exposed directly to the DAG construct. We've addressed the issu... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:2"
] | 128 | en | 0.35 | 2026-09-21T12:13:31.465519Z |
aip-0075-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — Compatibility and Migration | Title: AIP-75: New Asset-Centric Syntax — Compatibility and Migration
Proposal: AIP-75 | Project: airflow | State: unknown
## Compatibility and Migration
Since this is a strictly new syntax that is implemented with existing constructs, there should be no compatibility issues since existing code does not change behavi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:3"
] | 124 | en | 0.35 | 2026-09-21T12:13:31.465522Z |
aip-0075-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — Better UI display for `@asset` | Title: AIP-75: New Asset-Centric Syntax — Better UI display for `@asset`
Proposal: AIP-75 | Project: airflow | State: unknown
## Better UI display for `@asset`
As mentioned above, using the existing DAG view to display assets is not optimal, since an asset generally have very few, or even just one task body inside. W... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:4"
] | 160 | en | 0.35 | 2026-09-21T12:13:31.465525Z |
aip-0075-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627076 | Apache-2.0 | AIP-75: New Asset-Centric Syntax — Scope Definition | Title: AIP-75: New Asset-Centric Syntax — Scope Definition
Proposal: AIP-75 | Project: airflow | State: unknown
## Scope Definition
This AIP is considered complete when the `@asset` decorator is implemented and can fulfill the above features, and accompanying non-code materials are created. Scheduling and partitionin... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:75",
"proposal_state:unknown",
"chunk:5"
] | 305 | en | 0.575 | 2026-09-21T12:13:31.465528Z |
aip-0076-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Motivation | Title: AIP-76: Asset Partitions — Motivation
Proposal: AIP-76 | Project: airflow | State: unknown
This AIP is part of AIP-73, which aims to expand data awareness within Airflow.
## Motivation
Partitions are a critical enhancement to Airflow's data processing capabilities, designed to address some limitations in the ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:0"
] | 318 | en | 0.575 | 2026-09-21T12:13:27.321596Z |
aip-0076-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Rationale | Title: AIP-76: Asset Partitions — Rationale
Proposal: AIP-76 | Project: airflow | State: unknown
## Rationale
The idea behind partitions is to provide a way to model and organize data that is closely related, but still distinct, decoupling it from the task. For example, a daily-partitioned table for sales orders coul... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:1"
] | 696 | en | 0.525 | 2026-09-21T12:13:27.321608Z |
aip-0076-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Time-based Partitions | Title: AIP-76: Asset Partitions — Specification › Time-based Partitions
Proposal: AIP-76 | Project: airflow | State: unknown
### Time-based Partitions
These are similar to logical dates (more accurately, data intervals) today, and are meant to represent time or date ranges. Like today, they can automatically be deriv... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:3"
] | 362 | en | 0.55 | 2026-09-21T12:13:27.321615Z |
aip-0076-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Combined Partitions | Title: AIP-76: Asset Partitions — Specification › Combined Partitions
Proposal: AIP-76 | Project: airflow | State: unknown
### Combined Partitions
You will also be able to combine time-based and segment-based partitions.
```
@asset( schedule=dwh_daily_cloud_spend, partition=PartitionByProduct( [Partiti... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:4"
] | 97 | en | 0.35 | 2026-09-21T12:13:27.321618Z |
aip-0076-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Runtime-assigned Partitions | Title: AIP-76: Asset Partitions — Specification › Runtime-assigned Partitions
Proposal: AIP-76 | Project: airflow | State: unknown
### Runtime-assigned Partitions
All cases discussed up until now know the partition key up-front, and therefore can provide the key to a particular function run. Sometimes, however, parti... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:5"
] | 204 | en | 0.525 | 2026-09-21T12:13:27.321621Z |
aip-0076-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Rich Partition Key | Title: AIP-76: Asset Partitions — Specification › Rich Partition Key
Proposal: AIP-76 | Project: airflow | State: unknown
### Rich Partition Key
Internally, each partition is identified by its partition key. Although a primitive value (like a date, or a string) can satisfy basic use cases, real-world scenarios most l... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:6"
] | 245 | en | 0.525 | 2026-09-21T12:13:27.321624Z |
aip-0076-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Partition Dependency | Title: AIP-76: Asset Partitions — Specification › Partition Dependency
Proposal: AIP-76 | Project: airflow | State: unknown
### Partition Dependency
When an asset is scheduled against an upstream, and the two assets have the same partitioning logic, each partition of the downstream depends on the corresponding partit... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:8"
] | 220 | en | 0.525 | 2026-09-21T12:13:27.321630Z |
aip-0076-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Specification › Backfilling | Title: AIP-76: Asset Partitions — Specification › Backfilling
Proposal: AIP-76 | Project: airflow | State: unknown
### Backfilling
With the context of partitions, backfilling is an operation that retroactively materializes time-based partitions in the past. Only assets with time-based partitioning can be backfilled—t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:9"
] | 173 | en | 0.375 | 2026-09-21T12:13:27.321634Z |
aip-0076-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Implications for Dags and DagRuns | Title: AIP-76: Asset Partitions — Implications for Dags and DagRuns
Proposal: AIP-76 | Project: airflow | State: unknown
## Implications for Dags and DagRuns
### Overview
The asset decorator is just a wrapper that generates a dag with one task. So to have "partitioned assets", we need to have a dag that is scheduled... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:11"
] | 301 | en | 0.45 | 2026-09-21T12:13:27.321640Z |
aip-0076-12 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311626969 | Apache-2.0 | AIP-76: Asset Partitions — Future Work | Title: AIP-76: Asset Partitions — Future Work
Proposal: AIP-76 | Project: airflow | State: unknown
## Future Work
Topics listed in this section are incremental enhancements to the core concepts, and can be implemented at any point without breaking compatibility. They may still be implemented and released with other p... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:76",
"proposal_state:unknown",
"chunk:12"
] | 852 | en | 0.725 | 2026-09-21T12:13:27.321643Z |
aip-0077-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627079 | Apache-2.0 | AIP-77: Asset Validations — Motivation | Title: AIP-77: Asset Validations — Motivation
Proposal: AIP-77 | Project: airflow | State: unknown
## Motivation
## Rationale
To increase data reliability, we propose adding capabilities for data consumers and data producers to define and verify expectations around input and output assets via Operators and/or Asset ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:77",
"proposal_state:unknown",
"chunk:0"
] | 296 | en | 0.55 | 2026-09-21T12:13:28.896877Z |
aip-0078-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627729 | Apache-2.0 | AIP-78: Scheduler-managed backfill — Motivation | Title: AIP-78: Scheduler-managed backfill — Motivation
Proposal: AIP-78 | Project: airflow | State: unknown
## Motivation
### Backfill is currently CLI only
Backfill can only be invoked via CLI, but users don't always have access to the CLI. And since backfill is a synchronous ad hoc processes, if the CLI process di... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:78",
"proposal_state:unknown",
"chunk:0"
] | 236 | en | 0.475 | 2026-09-21T12:13:30.086246Z |
aip-0078-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627729 | Apache-2.0 | AIP-78: Scheduler-managed backfill — Considerations | Title: AIP-78: Scheduler-managed backfill — Considerations
Proposal: AIP-78 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
- Remove the backfill scheduler
- Make a "backfill job" a first class citizen
- CLI backfill will no longer run any tasks; it will create a backfil... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:78",
"proposal_state:unknown",
"chunk:1"
] | 1,266 | en | 0.65 | 2026-09-21T12:13:30.086252Z |
aip-0078-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627729 | Apache-2.0 | AIP-78: Scheduler-managed backfill — Out of scope | Title: AIP-78: Scheduler-managed backfill — Out of scope
Proposal: AIP-78 | Project: airflow | State: unknown
## Out of scope
#### "Other kinds" of backfill
This AIP is focused on how backfill is invoked and observed and managed, but not what backfill means. Other AIPs are looking at evolving airflow's data awarenes... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:78",
"proposal_state:unknown",
"chunk:2"
] | 140 | en | 0.375 | 2026-09-21T12:13:30.086255Z |
aip-0078-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627729 | Apache-2.0 | AIP-78: Scheduler-managed backfill — Interactions with other AIPs | Title: AIP-78: Scheduler-managed backfill — Interactions with other AIPs
Proposal: AIP-78 | Project: airflow | State: unknown
## Interactions with other AIPs
Other AIPs may have some impact on how this AIP shakes out. For example, currently, the dag run table is the store of data completeness state in Airflow, and yo... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:78",
"proposal_state:unknown",
"chunk:3"
] | 125 | en | 0.4 | 2026-09-21T12:13:30.086258Z |
aip-0078-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627729 | Apache-2.0 | AIP-78: Scheduler-managed backfill — What defines this AIP as "done"? | Title: AIP-78: Scheduler-managed backfill — What defines this AIP as "done"?
Proposal: AIP-78 | Project: airflow | State: unknown
## What defines this AIP as "done"?
- There are API endpoints that allow CRUD operations for backfill runs
- We can create a backfill run for a particular time range and scheduler will cre... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:78",
"proposal_state:unknown",
"chunk:4"
] | 115 | en | 0.4 | 2026-09-21T12:13:30.086261Z |
aip-0079-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627974 | Apache-2.0 | AIP-79: Remove Flask AppBuilder as Core dependency — Goals | Title: AIP-79: Remove Flask AppBuilder as Core dependency — Goals
Proposal: AIP-79 | Project: airflow | State: unknown
## Goals
- Have a smooth migration path from Airflow 2 to Airflow 3, in particular for authn/authz
- Set ourselves up for a true "FAB-free" future (while also making it possible today)
- If possible,... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:79",
"proposal_state:unknown",
"chunk:1"
] | 672 | en | 0.425 | 2026-09-21T12:13:31.566026Z |
aip-0082-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493498 | Apache-2.0 | AIP-82: External event driven scheduling in Airflow — Motivation | Title: AIP-82: External event driven scheduling in Airflow — Motivation
Proposal: AIP-82 | Project: airflow | State: unknown
## Motivation
Apache Airflow is primarily designed for time-based and dependency-based scheduling of workflows. However, modern data architectures often require near real-time processing and th... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:82",
"proposal_state:unknown",
"chunk:0"
] | 353 | en | 0.6 | 2026-09-21T12:13:31.606728Z |
aip-0082-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493498 | Apache-2.0 | AIP-82: External event driven scheduling in Airflow — Design | Title: AIP-82: External event driven scheduling in Airflow — Design
Proposal: AIP-82 | Project: airflow | State: unknown
## Design
The goal is to build a solution in Airflow to automatically update Assets based on external events. This scheduling can be categorized into two categories:
- Poll based event-driven sche... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:82",
"proposal_state:unknown",
"chunk:1"
] | 926 | en | 0.55 | 2026-09-21T12:13:31.606736Z |
aip-0082-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493498 | Apache-2.0 | AIP-82: External event driven scheduling in Airflow — Out of scope | Title: AIP-82: External event driven scheduling in Airflow — Out of scope
Proposal: AIP-82 | Project: airflow | State: unknown
## Out of scope
Items below are out of scope of this AIP. However, I decided to keep them in this document because they might be useful to initiate a conversation if someone decides to work o... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:82",
"proposal_state:unknown",
"chunk:2"
] | 638 | en | 0.475 | 2026-09-21T12:13:31.606740Z |
aip-0082-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493498 | Apache-2.0 | AIP-82: External event driven scheduling in Airflow — Considerations | Title: AIP-82: External event driven scheduling in Airflow — Considerations
Proposal: AIP-82 | Project: airflow | State: unknown
## Considerations
### What problem does it solve?
- Lack of native support for event-driven workflows in Airflow
- Difficulty in integrating Airflow with real-time data sources and message... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:82",
"proposal_state:unknown",
"chunk:3"
] | 232 | en | 0.45 | 2026-09-21T12:13:31.606743Z |
aip-0083-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493704 | Apache-2.0 | AIP-83: Rename execution_date -> logical_date and make logical_date optional | Title: AIP-83: Rename execution_date -> logical_date and make logical_date optional
Proposal: AIP-83 | Project: airflow | State: unknown
# Motivation
### On execution_date uniqueness / requiredness
Since inception, Airflow has used `execution_date` to distinguish different runs of a DAG. It's essentially what define... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:83",
"proposal_state:unknown",
"chunk:0"
] | 774 | en | 0.5 | 2026-09-21T12:13:32.800782Z |
aip-0084-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493907 | Apache-2.0 | AIP-84: UI REST API — Motivation | Title: AIP-84: UI REST API — Motivation
Proposal: AIP-84 | Project: airflow | State: unknown
## Motivation
Today, the interaction between the frontend and backend is quite messy and inconsistent. In AIP-79 Replace Flask AppBuilder, we plan to remove much of FAB. We will need to rewrite a lot of endpoints, so we shoul... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:84",
"proposal_state:unknown",
"chunk:0"
] | 441 | en | 0.425 | 2026-09-21T12:13:30.052683Z |
aip-0084-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315493907 | Apache-2.0 | AIP-84: UI REST API — Proposal | Title: AIP-84: UI REST API — Proposal
Proposal: AIP-84 | Project: airflow | State: unknown
## Proposal
We should try to add as much as possible to the public REST API but for what doesn't make sense for that should exist in its own UI REST API. The React UI will consume both, and only communicate to the backend throu... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:84",
"proposal_state:unknown",
"chunk:1"
] | 231 | en | 0.425 | 2026-09-21T12:13:30.052688Z |
aip-0085-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315494137 | Apache-2.0 | AIP-85: DAG importer — Motivation | Title: AIP-85: DAG importer — Motivation
Proposal: AIP-85 | Project: airflow | State: unknown
## Motivation
### What problem does it solve? / Why is it needed?
This AIP is a scoped-down, modified part of bigger initiative, which aims to establish **extendable DAG parsing controls** within Airflow. We've strategicall... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:85",
"proposal_state:unknown",
"chunk:0"
] | 615 | en | 0.5 | 2026-09-21T12:13:27.161434Z |
aip-0085-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315494137 | Apache-2.0 | AIP-85: DAG importer — Considerations › What change do you propose to make? | Title: AIP-85: DAG importer — Considerations › What change do you propose to make?
Proposal: AIP-85 | Project: airflow | State: unknown
### What change do you propose to make?
The high-level architecture centers on a modular registry-based approach, decoupling DAG discovery from parsing. This enables support for dive... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:85",
"proposal_state:unknown",
"chunk:1"
] | 1,520 | en | 0.55 | 2026-09-21T12:13:27.161442Z |
aip-0085-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315494137 | Apache-2.0 | AIP-85: DAG importer — Considerations › What change do you propose to make? | Title: AIP-85: DAG importer — Considerations › What change do you propose to make?
Proposal: AIP-85 | Project: airflow | State: unknown
**Proposal for Airflow Configuration changes**
This section defines the mapping between DAG bundles and their corresponding importer logic. The configuration can be part of [dag_proc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:85",
"proposal_state:unknown",
"chunk:2"
] | 269 | en | 0.45 | 2026-09-21T12:13:27.161446Z |
aip-0085-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315494137 | Apache-2.0 | AIP-85: DAG importer — Considerations › Defining a custom importer interface | Title: AIP-85: DAG importer — Considerations › Defining a custom importer interface
Proposal: AIP-85 | Project: airflow | State: unknown
### Defining a custom importer interface
Users or developers must create a class that inherits from AbstractDagImporter and implements its core interface. The custom importer dictat... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:85",
"proposal_state:unknown",
"chunk:3"
] | 98 | en | 0.35 | 2026-09-21T12:13:27.161449Z |
aip-0085-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=315494137 | Apache-2.0 | AIP-85: DAG importer — Considerations › Configuring the Importer via Airflow Configuration | Title: AIP-85: DAG importer — Considerations › Configuring the Importer via Airflow Configuration
Proposal: AIP-85 | Project: airflow | State: unknown
### Configuring the Importer via Airflow Configuration
Custom importers are registered directly in the Airflow configuration file (or via environment variables). Airfl... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:85",
"proposal_state:unknown",
"chunk:4"
] | 752 | en | 0.55 | 2026-09-21T12:13:27.161453Z |
aip-0086-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Summary | Title: AIP-86: Deadline Alerts (Formerly SLA) — Summary
Proposal: AIP-86 | Project: airflow | State: unknown
## Summary
The existing SLA implementation before Airflow 3.0 has been problematic and a constant point of debate. In the Airflow 3 planning meetings, it was discussed and decided that the move to a new major ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:0"
] | 271 | en | 0.425 | 2026-09-21T12:13:30.164384Z |
aip-0086-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Motivation | Title: AIP-86: Deadline Alerts (Formerly SLA) — Motivation
Proposal: AIP-86 | Project: airflow | State: unknown
## Motivation
### Problems in the Old Implementation
(credit for this section to Sung Yun in AIP-57)
- Sla_miss was evaluated only if the task_id had ever been in SUCCESS or SKIPPED state. This means that... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:1"
] | 324 | en | 0.45 | 2026-09-21T12:13:30.164391Z |
aip-0086-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Considerations | Title: AIP-86: Deadline Alerts (Formerly SLA) — Considerations
Proposal: AIP-86 | Project: airflow | State: unknown
## Considerations
As stated above, this AIP intentionally ignores all previous discussion on the topic or fixing, changing, redefining, or re-implementing "SLA". Previous discussions have been ongoing f... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:2"
] | 305 | en | 0.45 | 2026-09-21T12:13:30.164395Z |
aip-0086-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Why is it needed? | Title: AIP-86: Deadline Alerts (Formerly SLA) — Why is it needed?
Proposal: AIP-86 | Project: airflow | State: unknown
## Why is it needed?
Before diving into the challenges with the current SLA feature, let's consider what our users are expecting from an SLA feature in Airflow:
(Credit for user stories to Shubham M... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:3"
] | 337 | en | 0.5 | 2026-09-21T12:13:30.164398Z |
aip-0086-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — What change do you propose to make? | Title: AIP-86: Deadline Alerts (Formerly SLA) — What change do you propose to make?
Proposal: AIP-86 | Project: airflow | State: unknown
## What change do you propose to make?
- In dag_processing/processor.py add "save next SLA":
- If this DAG has a Deadline configured, then calculate the "need-by" and store the time... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:4"
] | 459 | en | 0.55 | 2026-09-21T12:13:30.164401Z |
aip-0086-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — How are users affected by the change? (e.g. DB upgrade required?) | Title: AIP-86: Deadline Alerts (Formerly SLA) — How are users affected by the change? (e.g. DB upgrade required?)
Proposal: AIP-86 | Project: airflow | State: unknown
## How are users affected by the change? (e.g. DB upgrade required?)
The SLAMiss table has been removed in 3.0 and this implementation will likely repl... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:6"
] | 118 | en | 0.35 | 2026-09-21T12:13:30.164407Z |
aip-0086-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — What defines this AIP as "done"? | Title: AIP-86: Deadline Alerts (Formerly SLA) — What defines this AIP as "done"?
Proposal: AIP-86 | Project: airflow | State: unknown
## What defines this AIP as "done"?
This AIP will only cover DAG-level Deadlines.
Appendices
## Appendix 1: Future Work
Future work could add:
- Task-level Deadlines (Task within a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:7"
] | 110 | en | 0.35 | 2026-09-21T12:13:30.164410Z |
aip-0086-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Appendix 2: Other timestamps in the databases that could possibly be used | Title: AIP-86: Deadline Alerts (Formerly SLA) — Appendix 2: Other timestamps in the databases that could possibly be used
Proposal: AIP-86 | Project: airflow | State: unknown
## Appendix 2: Other timestamps in the databases that could possibly be used
This is a list of all timestamps in the DB, included purely to ins... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:8"
] | 479 | en | 0.45 | 2026-09-21T12:13:30.164414Z |
aip-0086-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Test Procedure: | Title: AIP-86: Deadline Alerts (Formerly SLA) — Test Procedure:
Proposal: AIP-86 | Project: airflow | State: unknown
## Test Procedure:
For each test case:
- Create a new DAG configured with the specified DeadlineReference, interval, and callback in the Dag's `deadline`
- Configure the specified number of 30-second ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:9"
] | 209 | en | 0.45 | 2026-09-21T12:13:30.164417Z |
aip-0086-10 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 | Apache-2.0 | AIP-86: Deadline Alerts (Formerly SLA) — Baseline Test: | Title: AIP-86: Deadline Alerts (Formerly SLA) — Baseline Test:
Proposal: AIP-86 | Project: airflow | State: unknown
## Baseline Test:
TC-000 should be creating a Dag without a Deadline and running it to confirm that the environment is working as expected.
Test Case | DeadlineReference | Callback Type | Number of 30s... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:86",
"proposal_state:unknown",
"chunk:10"
] | 385 | en | 0.45 | 2026-09-21T12:13:30.164420Z |
aip-0087-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488436 | Apache-2.0 | AIP-87: Run Sensors in Triggerer with AsyncBaseSensor — Proposal: | Title: AIP-87: Run Sensors in Triggerer with AsyncBaseSensor — Proposal:
Proposal: AIP-87 | Project: airflow | State: unknown
## Proposal:
The proposal is to introduce AsyncBaseSensor and implementing runtime rescheduling decisions to execute sensor efficiently. Additionally we leverage the 2.10 version a new trigger... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:87",
"proposal_state:unknown",
"chunk:2"
] | 457 | en | 0.525 | 2026-09-21T12:13:30.260968Z |
aip-0088-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=334760511 | Apache-2.0 | AIP-88: Streaming & lazy task expansion via long-running triggers — Short summary | Title: AIP-88: Streaming & lazy task expansion via long-running triggers — Short summary
Proposal: AIP-88 | Project: airflow | State: unknown
## Short summary
Allow Triggerers to yield **multiple events in a single trigger run**, enabling true streaming-style workflows for async operators (e.g., HttpOperator/MSGraphA... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:88",
"proposal_state:unknown",
"chunk:0"
] | 147 | en | 0.35 | 2026-09-21T12:13:32.714387Z |
aip-0088-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=334760511 | Apache-2.0 | AIP-88: Streaming & lazy task expansion via long-running triggers — Goals | Title: AIP-88: Streaming & lazy task expansion via long-running triggers — Goals
Proposal: AIP-88 | Project: airflow | State: unknown
## Goals
Allow triggers to yield
**many events**during a single run and have those events processed incrementally by the operator runtime/scheduler without repeated operator deferral ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:88",
"proposal_state:unknown",
"chunk:1"
] | 108 | en | 0.4 | 2026-09-21T12:13:32.714398Z |
aip-0088-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=334760511 | Apache-2.0 | AIP-88: Streaming & lazy task expansion via long-running triggers — High-level design | Title: AIP-88: Streaming & lazy task expansion via long-running triggers — High-level design
Proposal: AIP-88 | Project: airflow | State: unknown
## High-level design
### Key idea
Extend the triggerer-to-scheduler event path so that a single trigger run may produce a stream of events which the scheduler can incremen... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:88",
"proposal_state:unknown",
"chunk:2"
] | 654 | en | 0.55 | 2026-09-21T12:13:32.714402Z |
aip-0089-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Abstract | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Abstract
Proposal: AIP-89 | Project: airflow | State: unknown
## Abstract
This AIP proposes implementing a privacy-first, transparent, and community-governed telemetry system for Apache Airflow using the Apache Software Foundation's Matomo instance as the de... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:0"
] | 307 | en | 0.425 | 2026-09-21T12:13:29.998987Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.