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-0001-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89066609 | Apache-2.0 | AIP-1: Improve Airflow Security [Deps: AIP-43] — Meetings | Title: AIP-1: Improve Airflow Security [Deps: AIP-43] — Meetings
Proposal: AIP-1 | Project: airflow | State: unknown
It's quite difficult to define "Done" criteria for "improve security", however ideas from this AIP and later discussions, have been turned into smaller AIPs:
~~AIP-43 DAG Processor separation~~Complete... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:1",
"proposal_state:unknown",
"chunk:0"
] | 140 | en | 0.35 | 2026-09-21T12:13:29.021091Z |
aip-0001-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89066609 | Apache-2.0 | AIP-1: Improve Airflow Security [Deps: AIP-43] — Challenges | Title: AIP-1: Improve Airflow Security [Deps: AIP-43] — Challenges
Proposal: AIP-1 | Project: airflow | State: unknown
## Challenges
DAGs can be generated by DAG factories essentially creating a kind of sub-DSL in which DAGs are defined. From Airflow's point of view this creates a challenge as DAGs therefore are able... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:1",
"proposal_state:unknown",
"chunk:2"
] | 411 | en | 0.45 | 2026-09-21T12:13:29.021099Z |
aip-0002-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89066630 | Apache-2.0 | AIP-2: Simplify process launching | Title: AIP-2: Simplify process launching
Proposal: AIP-2 | Project: airflow | State: unknown
# Motivation
Launching of tasks is quite expensive. We launch 2 airflow managers (LocalTaskJob and — raw task) and 6 processes (<user shell> → "bash -c" → "python"). We can just rely on executing "airflow" directly as the uni... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:2",
"proposal_state:unknown",
"chunk:0"
] | 202 | en | 0.425 | 2026-09-21T12:13:31.844166Z |
aip-0004-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93324355 | Apache-2.0 | AIP-4: Automation of System Tests [Deps: AIP-47] — Motivation | Title: AIP-4: Automation of System Tests [Deps: AIP-47] — Motivation
Proposal: AIP-4 | Project: airflow | State: unknown
Par of this AIP is being implemented in AIP-47 New design of Airflow System Tests
## Motivation
In the Apache Airflow project, the contributors have a need to run system tests with external system... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:4",
"proposal_state:unknown",
"chunk:0"
] | 637 | en | 0.475 | 2026-09-21T12:13:29.033859Z |
aip-0004-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=93324355 | Apache-2.0 | AIP-4: Automation of System Tests [Deps: AIP-47] — Considerations | Title: AIP-4: Automation of System Tests [Deps: AIP-47] — Considerations
Proposal: AIP-4 | Project: airflow | State: unknown
## Considerations
### Requirements/Constraints
For now we can focus only on Google Cloud Platform operators and later reuse the learnings for other clouds/external services.
There are several... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:4",
"proposal_state:unknown",
"chunk:1"
] | 501 | en | 0.425 | 2026-09-21T12:13:29.033865Z |
aip-0005-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652082 | Apache-2.0 | AIP-5: DagFetcher | Title: AIP-5: DagFetcher
Proposal: AIP-5 | Project: airflow | State: unknown
# Motivation
Currently Airflow requires DAG files to be present on a file system that is accessible to the scheduler, webserver, and workers. Given that more and more people are running airflow in a distributed setup to achieve higher scalab... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:5",
"proposal_state:unknown",
"chunk:0"
] | 110 | en | 0.35 | 2026-09-21T12:13:30.342209Z |
aip-0005-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652082 | Apache-2.0 | AIP-5: DagFetcher — Option 1: DAG Repository (short term) | Title: AIP-5: DagFetcher — Option 1: DAG Repository (short term)
Proposal: AIP-5 | Project: airflow | State: unknown
## Option 1: DAG Repository (short term)
DAGs are persisted in remote filesystem-like storage and Airflow need to know where to find them. **DAG repository **is introduced to record the remote root dir... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:5",
"proposal_state:unknown",
"chunk:1"
] | 857 | en | 0.55 | 2026-09-21T12:13:30.342216Z |
aip-0006-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=99844429 | Apache-2.0 | AIP-6: Enforce the usage of a code formatter & linter — Motivation | Title: AIP-6: Enforce the usage of a code formatter & linter — Motivation
Proposal: AIP-6 | Project: airflow | State: unknown
## Motivation
I propose to enforce the usage of a linter and code formatter for Airflow so that all code is structured by the same conventions resulting in less inconsistent and more readable ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:6",
"proposal_state:unknown",
"chunk:0"
] | 780 | en | 0.55 | 2026-09-21T12:13:32.941796Z |
aip-0007-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=99844641 | Apache-2.0 | AIP-7: Simplified development workflow — Motivation | Title: AIP-7: Simplified development workflow — Motivation
Proposal: AIP-7 | Project: airflow | State: unknown
## Motivation
Currently, the workflow for submitting new contributions is very cumbersome. Just the process of running unit tests is a difficult process, be it that you want to run them locally or through cr... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:7",
"proposal_state:unknown",
"chunk:0"
] | 145 | en | 0.35 | 2026-09-21T12:13:32.695934Z |
aip-0007-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=99844641 | Apache-2.0 | AIP-7: Simplified development workflow — Why is this change needed? | Title: AIP-7: Simplified development workflow — Why is this change needed?
Proposal: AIP-7 | Project: airflow | State: unknown
## Why is this change needed?
- Being able to reproduce Travis CI environment should help in solving stability issues and decrease time/money used by Travis CI builds
- It will be easier to o... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:7",
"proposal_state:unknown",
"chunk:2"
] | 409 | en | 0.5 | 2026-09-21T12:13:32.695951Z |
aip-0008-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827303 | Apache-2.0 | AIP-8: Split Providers into Separate Packages for Airflow 2.0 | Title: AIP-8: Split Providers into Separate Packages for Airflow 2.0
Proposal: AIP-8 | Project: airflow | State: unknown
# Motivation
Apache Airflow integrates with many different software systems, with hooks and operators to Amazon Web Services, Google Cloud Platform, Microsoft Azure, and more. As cloud APIs evolve,... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:8",
"proposal_state:unknown",
"chunk:0"
] | 377 | en | 0.425 | 2026-09-21T12:13:34.315174Z |
aip-0008-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827303 | Apache-2.0 | AIP-8: Split Providers into Separate Packages for Airflow 2.0 — The current state of provider package automation | Title: AIP-8: Split Providers into Separate Packages for Airflow 2.0 — The current state of provider package automation
Proposal: AIP-8 | Project: airflow | State: unknown
## The current state of provider package automation
For now, the installation of airflow 1.10 can be augmented by adding the backport provider pac... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:8",
"proposal_state:unknown",
"chunk:1"
] | 277 | en | 0.425 | 2026-09-21T12:13:34.315180Z |
aip-0008-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827303 | Apache-2.0 | AIP-8: Split Providers into Separate Packages for Airflow 2.0 — The current state of constraint management | Title: AIP-8: Split Providers into Separate Packages for Airflow 2.0 — The current state of constraint management
Proposal: AIP-8 | Project: airflow | State: unknown
## The current state of constraint management
We currently have a special way of managing constraints as explained in https://github.com/apache/airflow/... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:8",
"proposal_state:unknown",
"chunk:2"
] | 658 | en | 0.425 | 2026-09-21T12:13:34.315183Z |
aip-0008-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827303 | Apache-2.0 | AIP-8: Split Providers into Separate Packages for Airflow 2.0 — Consequences | Title: AIP-8: Split Providers into Separate Packages for Airflow 2.0 — Consequences
Proposal: AIP-8 | Project: airflow | State: unknown
## Consequences
- the core "apache-airflow" package is stripped-off any providers for 2.0 release
- we have 57 new 'apache-airflow-providers-*' packages (for example 'apache-airflow-... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:8",
"proposal_state:unknown",
"chunk:3"
] | 279 | en | 0.45 | 2026-09-21T12:13:34.315186Z |
aip-0008-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100827303 | Apache-2.0 | AIP-8: Split Providers into Separate Packages for Airflow 2.0 — Known Problems and solutions | Title: AIP-8: Split Providers into Separate Packages for Airflow 2.0 — Known Problems and solutions
Proposal: AIP-8 | Project: airflow | State: unknown
## Known Problems and solutions
- There is a known problem with installing a provider's package when you develop Airflow and install 'airflow' and 'providers' in sepa... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:8",
"proposal_state:unknown",
"chunk:4"
] | 469 | en | 0.475 | 2026-09-21T12:13:34.315189Z |
aip-0010-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Motivation | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Motivation
Proposal: AIP-10 | Project: airflow | State: unknown
## Motivation
Current official Airflow image is rebuilt from the scratch every time new commit is done to the repo. It is a "mono-layered" one and does not use Docker's multi-layer ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:0"
] | 433 | en | 0.5 | 2026-09-21T12:13:34.406922Z |
aip-0010-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — What problem does it solve? | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — What problem does it solve?
Proposal: AIP-10 | Project: airflow | State: unknown
## What problem does it solve?
It solves the following problems with current Dockerfile and image:
- time needed to rebuild the image when anything changes is rath... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:1"
] | 287 | en | 0.475 | 2026-09-21T12:13:34.406929Z |
aip-0010-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Assumptions | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Assumptions
Proposal: AIP-10 | Project: airflow | State: unknown
### Assumptions
- There are two images to be built:
- "Airflow" image - slim image with only necessary Airflow dependencies
- "CI" image - fat image wi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:3"
] | 200 | en | 0.425 | 2026-09-21T12:13:34.406936Z |
aip-0010-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Terms | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Terms
Proposal: AIP-10 | Project: airflow | State: unknown
### Terms
**Multi-staging Dockerfile**- a Dockerfile that utilises multi-stage builds - allowing to have intermediate images that are used to build final ima... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:4"
] | 520 | en | 0.425 | 2026-09-21T12:13:34.406939Z |
aip-0010-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Changes that trigger rebuilds | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Changes that trigger rebuilds
Proposal: AIP-10 | Project: airflow | State: unknown
### Changes that trigger rebuilds
Those changes below are described starting from the most frequent ones - so staring backwards from ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:5"
] | 265 | en | 0.425 | 2026-09-21T12:13:34.406943Z |
aip-0010-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Observations during implementation of POC | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Observations during implementation of POC
Proposal: AIP-10 | Project: airflow | State: unknown
### Observations during implementation of POC
During implementation of POC for the multi-stage/multi-layered build, sever... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:6"
] | 381 | en | 0.425 | 2026-09-21T12:13:34.406946Z |
aip-0010-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Proposed setup of the DockerHub and Travis CI | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Proposed setup of the DockerHub and Travis CI
Proposal: AIP-10 | Project: airflow | State: unknown
### Proposed setup of the DockerHub and Travis CI
**DockerHub - DockerHub builds for the WIP**
- We should choose wh... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:9"
] | 464 | en | 0.475 | 2026-09-21T12:13:34.406956Z |
aip-0010-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Layers in the main image | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Layers in the main image
Proposal: AIP-10 | Project: airflow | State: unknown
### Layers in the main image
The main image has a number of layers, that make the image rebuilds incrementally depending on changes in the... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:11"
] | 421 | en | 0.475 | 2026-09-21T12:13:34.406962Z |
aip-0010-12 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Different types of builds | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Why is this change needed? › Different types of builds
Proposal: AIP-10 | Project: airflow | State: unknown
### Different types of builds
The images for Airflow are build for several scenarios - and the "**hook/build**" script with accompanying ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:12"
] | 258 | en | 0.425 | 2026-09-21T12:13:34.406965Z |
aip-0010-13 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100828709 | Apache-2.0 | AIP-10: Multi-layered and multi-stage official Airflow CI image — Build timings | Title: AIP-10: Multi-layered and multi-stage official Airflow CI image — Build timings
Proposal: AIP-10 | Project: airflow | State: unknown
## Build timings
### Mono-layered image build timings
Build timings for different scenarios
Those timings were measured during tests. Times are in HH:MM:SS.
The yellow rows in... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:10",
"proposal_state:unknown",
"chunk:13"
] | 1,001 | en | 0.475 | 2026-09-21T12:13:34.406968Z |
aip-0011-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103088341 | Apache-2.0 | AIP-11: Create a Landing Page for Apache Airflow | Title: AIP-11: Create a Landing Page for Apache Airflow
Proposal: AIP-11 | Project: airflow | State: unknown
# Motivation
Open Source Software needs to build a community to ensure its healthy growth. One of the tools used to build a community is the web site dedicated to the product. The goal behind building an open ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:11",
"proposal_state:unknown",
"chunk:0"
] | 211 | en | 0.425 | 2026-09-21T12:13:32.893454Z |
aip-0011-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103088341 | Apache-2.0 | AIP-11: Create a Landing Page for Apache Airflow — Knowledge Architecture | Title: AIP-11: Create a Landing Page for Apache Airflow — Knowledge Architecture
Proposal: AIP-11 | Project: airflow | State: unknown
## Knowledge Architecture
OSS projects' websites typically include several standard pages, where each page is formatted with a navigation bar on the left.
Taking from best practices a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:11",
"proposal_state:unknown",
"chunk:1"
] | 473 | en | 0.45 | 2026-09-21T12:13:32.893461Z |
aip-0011-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103088341 | Apache-2.0 | AIP-11: Create a Landing Page for Apache Airflow — Content generation | Title: AIP-11: Create a Landing Page for Apache Airflow — Content generation
Proposal: AIP-11 | Project: airflow | State: unknown
## Content generation
Content of the website will include both auto-generated Pydocs for Documentation page and static front-end pages for the rest of the website.
All content will be dev... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:11",
"proposal_state:unknown",
"chunk:3"
] | 991 | en | 0.45 | 2026-09-21T12:13:32.893468Z |
aip-0012-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103088371 | Apache-2.0 | AIP-12: Persist DAG into DB | Title: AIP-12: Persist DAG into DB
Proposal: AIP-12 | Project: airflow | State: unknown
Video of current problem: https://www.youtube.com/watch?v=sNrBruPS3r4
We propose to persist all information of a DAG.py file in the Airflow metastore and make the webserver read the state from the metastore instead of parsing the ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:12",
"proposal_state:unknown",
"chunk:0"
] | 395 | en | 0.45 | 2026-09-21T12:13:32.674737Z |
aip-0013-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103088709 | Apache-2.0 | AIP-13: OpenAPI 3 based API definition — Proposal | Title: AIP-13: OpenAPI 3 based API definition — Proposal
Proposal: AIP-13 | Project: airflow | State: unknown
## Proposal
Develop an a JSON restful API using the existing Plugin interface, defined by OpenAPI 3.
## Implementation
### API Definition
The API will be defined by a YAML OpenAPI 3 definition, which will ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:13",
"proposal_state:unknown",
"chunk:1"
] | 490 | en | 0.45 | 2026-09-21T12:13:34.064087Z |
aip-0014-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103091837 | Apache-2.0 | AIP-14: Create composable operators using common interfaces — Considerations | Title: AIP-14: Create composable operators using common interfaces — Considerations
Proposal: AIP-14 | Project: airflow | State: unknown
## Considerations
To prevent a ton of A-to-B operators, we could create hooks which are accessible via a common interface. This allows for interchangeable operators, e.g. CopyOperat... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:14",
"proposal_state:unknown",
"chunk:1"
] | 212 | en | 0.425 | 2026-09-21T12:13:34.153822Z |
aip-0015-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103098286 | Apache-2.0 | AIP-15: Scalable Scheduler [ARCHIVED] — Benefits | Title: AIP-15: Scalable Scheduler [ARCHIVED] — Benefits
Proposal: AIP-15 | Project: airflow | State: unknown
This document is archived and replaced by: AIP-15 Support Multiple-Schedulers for HA & Better Scheduling Performance
Looking at the original AIP-15 the author proposes to use locking to enable the use of multi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:15",
"proposal_state:unknown",
"chunk:0"
] | 126 | en | 0.35 | 2026-09-21T12:13:31.876468Z |
aip-0015-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103098286 | Apache-2.0 | AIP-15: Scalable Scheduler [ARCHIVED] — Processes | Title: AIP-15: Scalable Scheduler [ARCHIVED] — Processes
Proposal: AIP-15 | Project: airflow | State: unknown
## Processes
### MainScheduler
This process should always run, like the current scheduler.
This process can be master/failover or this can be solved within k8s as discussed in AIP-15 Support Multiple-Schedu... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:15",
"proposal_state:unknown",
"chunk:1"
] | 207 | en | 0.45 | 2026-09-21T12:13:31.876473Z |
aip-0017-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093484 | Apache-2.0 | AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — -- Motivation | Title: AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — -- Motivation
Proposal: AIP-17 | Project: airflow | State: unknown
### -- Motivation
In our experience with airflow, we found that the resource utilization is very low. We need a lot of worker machines to support all the concurrent run... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:17",
"proposal_state:unknown",
"chunk:0"
] | 530 | en | 0.475 | 2026-09-21T12:13:34.295302Z |
aip-0017-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093484 | Apache-2.0 | AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — -- What is Smart Sensor | Title: AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — -- What is Smart Sensor
Proposal: AIP-17 | Project: airflow | State: unknown
### -- What is Smart Sensor
The smart sensor is a service which greatly reduces airflow's infrastructure cost by consolidating some of the airflow long runnin... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:17",
"proposal_state:unknown",
"chunk:1"
] | 424 | en | 0.45 | 2026-09-21T12:13:34.295308Z |
aip-0017-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093484 | Apache-2.0 | AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — Change summary: | Title: AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — Change summary:
Proposal: AIP-17 | Project: airflow | State: unknown
### Change summary:
- Add a new mode called "smart sensor mode". In smart sensor mode, instead of holding a long running process for each sensor and poking periodical... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:17",
"proposal_state:unknown",
"chunk:2"
] | 1,195 | en | 0.5 | 2026-09-21T12:13:34.295312Z |
aip-0017-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093484 | Apache-2.0 | AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — How to enable/disable smart sensor | Title: AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — How to enable/disable smart sensor
Proposal: AIP-17 | Project: airflow | State: unknown
### How to enable/disable smart sensor
Enabling/Disabling the smart sensor is a system level config which is transparent to the individual users. A... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:17",
"proposal_state:unknown",
"chunk:3"
] | 188 | en | 0.45 | 2026-09-21T12:13:34.295315Z |
aip-0017-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093484 | Apache-2.0 | AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — How to support new operators | Title: AIP-17: Consolidate and de-duplicate sensor tasks in airflow Smart Sensor — How to support new operators
Proposal: AIP-17 | Project: airflow | State: unknown
### How to support new operators
- Define "poke_context_fields" as class attribute in the operator. "poke_context_fields" include all key names used for ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:17",
"proposal_state:unknown",
"chunk:4"
] | 265 | en | 0.425 | 2026-09-21T12:13:34.295318Z |
aip-0018-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103098300 | Apache-2.0 | AIP-18: Persist all information from DAG file in DB — Motivation | Title: AIP-18: Persist all information from DAG file in DB — Motivation
Proposal: AIP-18 | Project: airflow | State: unknown
## Motivation
As a follow up on AIP-19 (making the webserver stateless) I suggest to store the DAG structure and metadata in the database. Where AIP-19 targets the webserver to read only from t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:18",
"proposal_state:unknown",
"chunk:0"
] | 650 | en | 0.45 | 2026-09-21T12:13:34.345539Z |
aip-0019-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103098373 | Apache-2.0 | AIP-19: Making the webserver stateless — Motivation | Title: AIP-19: Making the webserver stateless — Motivation
Proposal: AIP-19 | Project: airflow | State: unknown
## Motivation
**** Note: this AIP replaces AIP-12 with a better defined scope that should help in the discussion surrounding the AIP. ****
**Issue**
In the current implementation, Gunicorn webserver proce... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:19",
"proposal_state:unknown",
"chunk:0"
] | 527 | en | 0.45 | 2026-09-21T12:13:32.683020Z |
aip-0020-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=109445731 | Apache-2.0 | AIP-20: DAG manifest — Motivation | Title: AIP-20: DAG manifest — Motivation
Proposal: AIP-20 | Project: airflow | State: unknown
## Motivation
Currently, DAGs are discovered by Airflow through traversing the all the files under $AIRFLOW_HOME/dags, looking for files that contains "airflow" and "DAG" in the content, which is not efficient. We need to fi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:20",
"proposal_state:unknown",
"chunk:0"
] | 487 | en | 0.55 | 2026-09-21T12:13:30.235246Z |
aip-0021-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115529665 | Apache-2.0 | AIP-21: Changes in import paths | Title: AIP-21: Changes in import paths
Proposal: AIP-21 | Project: airflow | State: unknown
# Motivation
During the 4-year project development, the community made many decisions about the structure and principles of module creation. Some decisions have been made by Airbnb and they no longer apply. Other recommendatio... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:21",
"proposal_state:unknown",
"chunk:0"
] | 1,051 | en | 0.6 | 2026-09-21T12:13:31.803136Z |
aip-0021-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115529665 | Apache-2.0 | AIP-21: Changes in import paths — Case #1 airflow.contrib.{resources} | Title: AIP-21: Changes in import paths — Case #1 airflow.contrib.{resources}
Proposal: AIP-21 | Project: airflow | State: unknown
## Case #1 airflow.contrib.{resources}
*There should be one-- and preferably only one --obvious way to do it.*
*Tim Peters, The Zen of Python*
Currently, resources are located in two pla... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:21",
"proposal_state:unknown",
"chunk:1"
] | 290 | en | 0.45 | 2026-09-21T12:13:31.803145Z |
aip-0021-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115529665 | Apache-2.0 | AIP-21: Changes in import paths — Case #3 {aws/azure/gcp}_* | Title: AIP-21: Changes in import paths — Case #3 {aws/azure/gcp}_*
Proposal: AIP-21 | Project: airflow | State: unknown
## Case #3 {aws/azure/gcp}_*
With the development of integration for the largest cloud providers, a large part of new files received a prefix, which is assigned to each of them. For example, for Goo... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:21",
"proposal_state:unknown",
"chunk:3"
] | 558 | en | 0.425 | 2026-09-21T12:13:31.803152Z |
aip-0021-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115529665 | Apache-2.0 | AIP-21: Changes in import paths — Case #5 *Operator | Title: AIP-21: Changes in import paths — Case #5 *Operator
Proposal: AIP-21 | Project: airflow | State: unknown
## Case #5 *Operator
Class name does not need suffix "Operator"
**Solution A:**
~~We can delete the suffix "Operator" from the class name~~
~~Example:~~
Class GcpTransferServiceJobDeleteOperator should ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:21",
"proposal_state:unknown",
"chunk:4"
] | 237 | en | 0.425 | 2026-09-21T12:13:31.803155Z |
aip-0022-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=119550296 | Apache-2.0 | AIP-22: Group ORM models by their logical usage instead of type — Motivation | Title: AIP-22: Group ORM models by their logical usage instead of type — Motivation
Proposal: AIP-22 | Project: airflow | State: unknown
## Motivation
I propose to move all SQLAlchemy ORM classes to the folder where they logically belong to, instead of grouping by type. From a user perspective I think this makes more... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:22",
"proposal_state:unknown",
"chunk:0"
] | 313 | en | 0.45 | 2026-09-21T12:13:34.136105Z |
aip-0023-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122916333 | Apache-2.0 | AIP-23: Migrate out of Travis CI — Motivation | Title: AIP-23: Migrate out of Travis CI — Motivation
Proposal: AIP-23 | Project: airflow | State: unknown
## Motivation
We have recently started to experience a lot of problems with TravisCI. They are documented in https://lists.apache.org/thread.html/8bfee0f0a52b7b8b9ec63724c48f76a7002aeacf7c86c5a23b48f172@%3Cdev.ai... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:23",
"proposal_state:unknown",
"chunk:0"
] | 1,128 | en | 0.425 | 2026-09-21T12:13:32.848202Z |
aip-0024-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122917224 | Apache-2.0 | AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — Motivation | Title: AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — Motivation
Proposal: AIP-24 | Project: airflow | State: unknown
## Motivation
This doc proposes an approach that serializes/persists DAGs using JSON to decouple Airflow webserver from DAG parsing and accelerating schedule... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:24",
"proposal_state:unknown",
"chunk:0"
] | 315 | en | 0.5 | 2026-09-21T12:13:34.821156Z |
aip-0024-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122917224 | Apache-2.0 | AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 2. DAG Serialization | Title: AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 2. DAG Serialization
Proposal: AIP-24 | Project: airflow | State: unknown
## 2. DAG Serialization
### 2.1 Current Options in Airflow (not work)
Airflow uses Pickle as the default approach for serializing. Airflow has tab... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:24",
"proposal_state:unknown",
"chunk:1"
] | 487 | en | 0.45 | 2026-09-21T12:13:34.821172Z |
aip-0024-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122917224 | Apache-2.0 | AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 3. Life Cycle of a Cached DAG | Title: AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 3. Life Cycle of a Cached DAG
Proposal: AIP-24 | Project: airflow | State: unknown
## 3. Life Cycle of a Cached DAG
#### 3.1 DB Schema Change
Storing serialized DAGs requires a new table serialized_dags (a few more colum... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:24",
"proposal_state:unknown",
"chunk:2"
] | 404 | en | 0.45 | 2026-09-21T12:13:34.821178Z |
aip-0024-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122917224 | Apache-2.0 | AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 4. Long-Term Roadmap with Other Proposals | Title: AIP-24: DAG Persistence in DB using JSON for Airflow Webserver and (optional) Scheduler — 4. Long-Term Roadmap with Other Proposals
Proposal: AIP-24 | Project: airflow | State: unknown
## 4. Long-Term Roadmap with Other Proposals
This AIP aims at implementing DAG persistence with minimal change on Airflow. It ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:24",
"proposal_state:unknown",
"chunk:3"
] | 408 | en | 0.45 | 2026-09-21T12:13:34.821183Z |
aip-0026-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132320277 | Apache-2.0 | AIP-26: Production-ready Airflow Docker Image — Motivation | Title: AIP-26: Production-ready Airflow Docker Image — Motivation
Proposal: AIP-26 | Project: airflow | State: unknown
## Motivation
As cloud goes Kubernetes native, Docker (or more precisely containers) becomes the default mechanism for packaging and running applications. We are currently using Docker images for Con... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:26",
"proposal_state:unknown",
"chunk:0"
] | 322 | en | 0.425 | 2026-09-21T12:13:32.766901Z |
aip-0026-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132320277 | Apache-2.0 | AIP-26: Production-ready Airflow Docker Image — Considerations | Title: AIP-26: Production-ready Airflow Docker Image — Considerations
Proposal: AIP-26 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
The proposal is to update the current CI-optimised Docker images of Airflow to build production-ready images. This image should retain p... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:26",
"proposal_state:unknown",
"chunk:1"
] | 541 | en | 0.475 | 2026-09-21T12:13:32.766906Z |
aip-0027-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=132321242 | Apache-2.0 | AIP-27: Migrate to pytest — Considerations | Title: AIP-27: Migrate to pytest — Considerations
Proposal: AIP-27 | Project: airflow | State: unknown
## Considerations
To understand how much work migration will required I've created PoC branch (https://github.com/PolideaInternal/airflow/pull/343). As a result I obtained a build that results in: 15 failed, 3592 pa... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:27",
"proposal_state:unknown",
"chunk:1"
] | 434 | en | 0.45 | 2026-09-21T12:13:31.419852Z |
aip-0028-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=143428432 | Apache-2.0 | AIP-28: Add AsyncExecutor option — WIP STATUS | Title: AIP-28: Add AsyncExecutor option — WIP STATUS
Proposal: AIP-28 | Project: airflow | State: unknown
## WIP STATUS
- This AIP is a work in progress to gather requirements and scope, together with sketches of possible implementation details
## Motivation
For long-running tasks (e.g. jobs on cloud providers), op... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:28",
"proposal_state:unknown",
"chunk:0"
] | 555 | en | 0.525 | 2026-09-21T12:13:31.841965Z |
aip-0028-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=143428432 | Apache-2.0 | AIP-28: Add AsyncExecutor option — Considerations | Title: AIP-28: Add AsyncExecutor option — Considerations
Proposal: AIP-28 | Project: airflow | State: unknown
## Considerations
Is there anything special to consider about this AIP? Downsides? Difficulty in implementation or rollout etc?
### What change do you propose to make?
For higher concurrency in some areas o... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:28",
"proposal_state:unknown",
"chunk:1"
] | 947 | en | 0.475 | 2026-09-21T12:13:31.841972Z |
aip-0029-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=143428948 | Apache-2.0 | AIP-29: AWS Fargate Executor — Motivation | Title: AIP-29: AWS Fargate Executor — Motivation
Proposal: AIP-29 | Project: airflow | State: unknown
## Motivation
For the past year my company has been leveraging an AWS Fargate Executor (since Airflow 1.10.2). We really want to give back to the Airflow community for building something so wonderful. We're also open... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:29",
"proposal_state:unknown",
"chunk:0"
] | 999 | en | 0.45 | 2026-09-21T12:13:31.651704Z |
aip-0030-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence | Title: AIP-30: State persistence
Proposal: AIP-30 | Project: airflow | State: unknown
# Motivation
For various reasons, it can be helpful to persist state arbitrary information for tasks or dags. For some pipelines, it may be strictly necessary.
One use case is incremental processes; incremental processes are a very... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:0"
] | 113 | en | 0.425 | 2026-09-21T12:13:27.526025Z |
aip-0030-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — What problem does it solve? | Title: AIP-30: State persistence — What problem does it solve?
Proposal: AIP-30 | Project: airflow | State: unknown
## What problem does it solve?
Below I enumerate a couple job patterns that benefit from state persistence.
The current mechanisms for storing state are problematic for reasons outlined below.
## Why ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:1"
] | 126 | en | 0.375 | 2026-09-21T12:13:27.526030Z |
aip-0030-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — Are there any downsides to this change? | Title: AIP-30: State persistence — Are there any downsides to this change?
Proposal: AIP-30 | Project: airflow | State: unknown
## Are there any downsides to this change?
Every option proposed here is a non-breaking change that is 100% backwards-compatible.
Some argue that incremental processes are a bad design patt... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:2"
] | 136 | en | 0.375 | 2026-09-21T12:13:27.526034Z |
aip-0030-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — Job patterns benefitting from state persistence | Title: AIP-30: State persistence — Job patterns benefitting from state persistence
Proposal: AIP-30 | Project: airflow | State: unknown
## Job patterns benefitting from state persistence
### Incremental processes
There are many kinds of tasks that fit this pattern. Examples:
- pulling from database based on datetim... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:4"
] | 261 | en | 0.55 | 2026-09-21T12:13:27.526040Z |
aip-0030-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — Problems with the existing approaches | Title: AIP-30: State persistence — Problems with the existing approaches
Proposal: AIP-30 | Project: airflow | State: unknown
## Problems with the existing approaches
Currently there are two ways to store state information in the metastore: Variables and XCom.
### XCom
XCom can be made to work as a mechanism of sta... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:5"
] | 414 | en | 0.525 | 2026-09-21T12:13:27.526043Z |
aip-0030-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — Solutions considered | Title: AIP-30: State persistence — Solutions considered
Proposal: AIP-30 | Project: airflow | State: unknown
## Solutions considered
### Solution 1: add column "is_stateful" to XCom
Add a boolean column `is_stateful` to XCom table. XCom records with `is_stateful=True` would not be cleared at task start. This would a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:6"
] | 691 | en | 0.525 | 2026-09-21T12:13:27.526046Z |
aip-0030-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=145722105 | Apache-2.0 | AIP-30: State persistence — Concrete proposal | Title: AIP-30: State persistence — Concrete proposal
Proposal: AIP-30 | Project: airflow | State: unknown
## Concrete proposal
### The proposal
I propose we add ProcessState, TaskState, and TaskInstanceState (solutions 3, 5 and 6).
### Reasoning
#### Why not add to xcom (solution 1)?
XCom is already a bit complic... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:30",
"proposal_state:unknown",
"chunk:7"
] | 261 | en | 0.425 | 2026-09-21T12:13:27.526049Z |
aip-0031-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148638736 | Apache-2.0 | AIP-31: "TaskFlow API" for clearer/simpler DAG definition — Motivation | Title: AIP-31: "TaskFlow API" for clearer/simpler DAG definition — Motivation
Proposal: AIP-31 | Project: airflow | State: unknown
## Motivation
Airflow does not currently have an explicit way to declare messages passed between tasks in a DAG. XCom are available but are hidden in execution functions inside the operat... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:31",
"proposal_state:unknown",
"chunk:0"
] | 141 | en | 0.4 | 2026-09-21T12:13:34.339197Z |
aip-0031-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148638736 | Apache-2.0 | AIP-31: "TaskFlow API" for clearer/simpler DAG definition — Considerations | Title: AIP-31: "TaskFlow API" for clearer/simpler DAG definition — Considerations
Proposal: AIP-31 | Project: airflow | State: unknown
## Considerations
What change do you propose to make?
The proposal end result is to provide an explicit way to declare message passing dependencies in a DAG. That can be accomplished... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:31",
"proposal_state:unknown",
"chunk:1"
] | 856 | en | 0.65 | 2026-09-21T12:13:34.339202Z |
aip-0032-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148639512 | Apache-2.0 | AIP-32: Airflow REST API — Background | Title: AIP-32: Airflow REST API — Background
Proposal: AIP-32 | Project: airflow | State: unknown
This document captures the design of REST API for Apache Airflow.
# Summary of Changes
N.o. | Version | Date | Description |
1 | v20200226 | 2020-02-26 | First version |
2 | v20200403 | 2020-04-03 | Adaptation of perm... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:32",
"proposal_state:unknown",
"chunk:0"
] | 282 | en | 0.425 | 2026-09-21T12:13:31.872252Z |
aip-0032-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148639512 | Apache-2.0 | AIP-32: Airflow REST API — Goal | Title: AIP-32: Airflow REST API — Goal
Proposal: AIP-32 | Project: airflow | State: unknown
## Goal
**Create solid fundamentals**
We want to develop a solution that meets the following basic requirements:
- It should be
**easy to maintain**- provides unified methods for major technical issues e.g. CRUD operations t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:32",
"proposal_state:unknown",
"chunk:1"
] | 441 | en | 0.45 | 2026-09-21T12:13:31.872258Z |
aip-0032-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148639512 | Apache-2.0 | AIP-32: Airflow REST API — Non-goal | Title: AIP-32: Airflow REST API — Non-goal
Proposal: AIP-32 | Project: airflow | State: unknown
## Non-goal
**API Client**
The API will not depend on the specific client implementation. Customers can use any language and technology to send requests to the API server. It will even be possible to use CURL/Bash to send... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:32",
"proposal_state:unknown",
"chunk:2"
] | 404 | en | 0.425 | 2026-09-21T12:13:31.872262Z |
aip-0032-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148639512 | Apache-2.0 | AIP-32: Airflow REST API — Current approach | Title: AIP-32: Airflow REST API — Current approach
Proposal: AIP-32 | Project: airflow | State: unknown
## Current approach
Airflow currently uses view-based permissions based on Flask App Builder. We have the following permissions:
can_add can_blocked can_chart can_clear can_code can_conf can_dag_details can_dag_ed... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:32",
"proposal_state:unknown",
"chunk:3"
] | 215 | en | 0.45 | 2026-09-21T12:13:31.872265Z |
aip-0032-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148639512 | Apache-2.0 | AIP-32: Airflow REST API — API generator based on the database model | Title: AIP-32: Airflow REST API — API generator based on the database model
Proposal: AIP-32 | Project: airflow | State: unknown
## API generator based on the database model
There are ready solutions that allow you to quickly create an API based on a database model. They have the following advantages:
- allow us to ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:32",
"proposal_state:unknown",
"chunk:5"
] | 260 | en | 0.425 | 2026-09-21T12:13:31.872272Z |
aip-0033-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148640972 | Apache-2.0 | AIP-33: Secrets backend — Motivation | Title: AIP-33: Secrets backend — Motivation
Proposal: AIP-33 | Project: airflow | State: unknown
## Motivation
Currently we can store connections in metastore or env variables.
As an airflow cluster maintainer, I want to be able to store connections in other sources e.g. AWS SSM parameter store. This would give me m... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:33",
"proposal_state:unknown",
"chunk:0"
] | 783 | en | 0.425 | 2026-09-21T12:13:30.352197Z |
aip-0034-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645525 | Apache-2.0 | AIP-34: TaskGroup: A UI task grouping concept as an alternative to SubDagOperator — Motivation | Title: AIP-34: TaskGroup: A UI task grouping concept as an alternative to SubDagOperator — Motivation
Proposal: AIP-34 | Project: airflow | State: unknown
## Motivation
Currently, the SubDagOperator launches a completely different DAG and then monitors it as a separate entity. This has lead to all sorts of edge case ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:34",
"proposal_state:unknown",
"chunk:0"
] | 150 | en | 0.35 | 2026-09-21T12:13:34.325690Z |
aip-0034-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645525 | Apache-2.0 | AIP-34: TaskGroup: A UI task grouping concept as an alternative to SubDagOperator — Considerations | Title: AIP-34: TaskGroup: A UI task grouping concept as an alternative to SubDagOperator — Considerations
Proposal: AIP-34 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
The goal of this proposal is to introduce a new concept called TaskGroup. It can be used as an alter... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:34",
"proposal_state:unknown",
"chunk:1"
] | 1,028 | en | 0.55 | 2026-09-21T12:13:34.325698Z |
aip-0035-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158863513 | Apache-2.0 | AIP-35: Add Signal Based Scheduling To Airflow — Motivation | Title: AIP-35: Add Signal Based Scheduling To Airflow — Motivation
Proposal: AIP-35 | Project: airflow | State: unknown
## Motivation
Airflow scheduler uses DAG definitions to monitor the state of tasks in the metadata database, and triggers the task instances whose dependencies have been met. It is based on state of... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:35",
"proposal_state:unknown",
"chunk:0"
] | 229 | en | 0.5 | 2026-09-21T12:13:34.087937Z |
aip-0035-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158863513 | Apache-2.0 | AIP-35: Add Signal Based Scheduling To Airflow — Considerations | Title: AIP-35: Add Signal Based Scheduling To Airflow — Considerations
Proposal: AIP-35 | Project: airflow | State: unknown
## Considerations
**Public Interfaces**
**Signal Operator**
- Introduce a new class of SignalOperator for the operators that send signals.
- Let BaseOperator inherit SignalOperator.
**Signal ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:35",
"proposal_state:unknown",
"chunk:1"
] | 845 | en | 0.55 | 2026-09-21T12:13:34.087944Z |
aip-0035-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158863513 | Apache-2.0 | AIP-35: Add Signal Based Scheduling To Airflow — Considerations › What change do you propose to make? | Title: AIP-35: Add Signal Based Scheduling To Airflow — Considerations › What change do you propose to make?
Proposal: AIP-35 | Project: airflow | State: unknown
### What change do you propose to make?
**Signal Operator**
Signal defines conditions that must be met for the action of the task instance. Scheduler switc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:35",
"proposal_state:unknown",
"chunk:2"
] | 744 | en | 0.45 | 2026-09-21T12:13:34.087948Z |
aip-0036-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158868919 | Apache-2.0 | AIP-36: DAG Versioning — Problem | Title: AIP-36: DAG Versioning — Problem
Proposal: AIP-36 | Project: airflow | State: unknown
## Problem
Within Airflow, data pipelines are represented by DAGs and these DAGs change over time as business needs evolve. A key challenge faced by Airflow users today is with looking at how a DAG was run in the past, when i... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:36",
"proposal_state:unknown",
"chunk:0"
] | 169 | en | 0.375 | 2026-09-21T12:13:30.283090Z |
aip-0036-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158868919 | Apache-2.0 | AIP-36: DAG Versioning — Scenarios | Title: AIP-36: DAG Versioning — Scenarios
Proposal: AIP-36 | Project: airflow | State: unknown
## Scenarios
The main scenarios considered and relevant to this proposal are outlined below.
**Scenario 1: View logs from a no longer existing task instance**
First version of the DAG has three tasks: Task A, Task B, and ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:36",
"proposal_state:unknown",
"chunk:1"
] | 893 | en | 0.45 | 2026-09-21T12:13:30.283096Z |
aip-0036-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158868919 | Apache-2.0 | AIP-36: DAG Versioning — Scenarios › Tree View | Title: AIP-36: DAG Versioning — Scenarios › Tree View
Proposal: AIP-36 | Project: airflow | State: unknown
### Tree View
**Update:** All task instance status boxes within the timeline will have an outline added around them. This will add contrast, especially to the white "no status" boxes. As depicted below, runs whe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:36",
"proposal_state:unknown",
"chunk:3"
] | 228 | en | 0.45 | 2026-09-21T12:13:30.283102Z |
aip-0036-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158868919 | Apache-2.0 | AIP-36: DAG Versioning — Scenarios › Graph View | Title: AIP-36: DAG Versioning — Scenarios › Graph View
Proposal: AIP-36 | Project: airflow | State: unknown
### Graph View
**Add:** For the selected DAG run, DAG Version Badges will be displayed in the legend area above the graph chart. If a given run consisted of more than one version, each version will be listed. S... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:36",
"proposal_state:unknown",
"chunk:4"
] | 101 | en | 0.35 | 2026-09-21T12:13:30.283105Z |
aip-0036-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158868919 | Apache-2.0 | AIP-36: DAG Versioning — Scenarios › Code View | Title: AIP-36: DAG Versioning — Scenarios › Code View
Proposal: AIP-36 | Project: airflow | State: unknown
### Code View
**Add:** Accept a URL parameter to pre-select which version of the DAG will be shown. When the parameter is not present, the latest version will be shown.
```java
/code?dag_id=gcp_billing_to_pg&da... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:36",
"proposal_state:unknown",
"chunk:6"
] | 686 | en | 0.55 | 2026-09-21T12:13:30.283111Z |
aip-0037-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173082045 | Apache-2.0 | AIP-37: Virtualenv management inside Airflow — Considerations | Title: AIP-37: Virtualenv management inside Airflow — Considerations
Proposal: AIP-37 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
In order to solve this issue, I suggest to introduce venv management as part of the celery and local executors lifecycle.
__Option A - m... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:37",
"proposal_state:unknown",
"chunk:1"
] | 455 | en | 0.45 | 2026-09-21T12:13:32.950703Z |
aip-0038-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Motivation | Title: AIP-38: Modern Web Application — Motivation
Proposal: AIP-38 | Project: airflow | State: unknown
## Motivation
While the Airflow UI did receive a recent facelift for the 2.0 release, the changes merely made it *look like* a modern web application, but not function as one. The current application has served Air... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:0"
] | 349 | en | 0.425 | 2026-09-21T12:13:30.047611Z |
aip-0038-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Technology | Title: AIP-38: Modern Web Application — Technology
Proposal: AIP-38 | Project: airflow | State: unknown
## Technology
### Proof of Concept
We've produced a POC that demonstrates how the resulting product may look and feel, using the technologies we seek to adopt. It fully utilizes the API of a remote Airflow instanc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:1"
] | 1,189 | en | 0.45 | 2026-09-21T12:13:30.047616Z |
aip-0038-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Information Architecture & Design Process | Title: AIP-38: Modern Web Application — Information Architecture & Design Process
Proposal: AIP-38 | Project: airflow | State: unknown
## Information Architecture & Design Process
When building (or re-building) any application from the ground up, it is a unique opportunity to make a holistic assessment of the Informa... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:2"
] | 327 | en | 0.425 | 2026-09-21T12:13:30.047620Z |
aip-0038-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Introduction Path (to end-users) | Title: AIP-38: Modern Web Application — Introduction Path (to end-users)
Proposal: AIP-38 | Project: airflow | State: unknown
## Introduction Path (to end-users)
Introduce new UI side-by-side (opt-in, easily switch between at a per-user level) with the current at minor version release. Remove/replace the current UI c... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:3"
] | 289 | en | 0.45 | 2026-09-21T12:13:30.047623Z |
aip-0038-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Proposed Process | Title: AIP-38: Modern Web Application — Proposed Process
Proposal: AIP-38 | Project: airflow | State: unknown
## Proposed Process
- AIP Feedback
- AIP Acceptance
- Begin design process with UI SIG (process expected to take 4-5 weeks)
- Continued development of POC until pre-determined feature set MVP
- API requiremen... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:4"
] | 214 | en | 0.425 | 2026-09-21T12:13:30.047626Z |
aip-0038-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087533 | Apache-2.0 | AIP-38: Modern Web Application — Airflow 3 Update: 7-11-2024 | Title: AIP-38: Modern Web Application — Airflow 3 Update: 7-11-2024
Proposal: AIP-38 | Project: airflow | State: unknown
## Airflow 3 Update: 7-11-2024
From Airflow 2.3 - 2.10, we took a different turn. Instead of developing an MVP and loading two separate UIs. We went forward with building a small React app that can... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:38",
"proposal_state:unknown",
"chunk:5"
] | 299 | en | 0.45 | 2026-09-21T12:13:30.047629Z |
aip-0039-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Motivation | Title: AIP-39: Richer scheduler_interval — Motivation
Proposal: AIP-39 | Project: airflow | State: unknown
## Motivation
Currently a DAG can be scheduled by either providing a cron expression (or one of the @ presets) or by passing a timedelta, and this works well for DAGs that need to operate on a regular schedule b... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:0"
] | 179 | en | 0.35 | 2026-09-21T12:13:30.334184Z |
aip-0039-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Desirable Schedule patterns | Title: AIP-39: Richer scheduler_interval — Desirable Schedule patterns
Proposal: AIP-39 | Project: airflow | State: unknown
## Desirable Schedule patterns
A few examples of the kind of workflows/schedule that I would like Airflow to be able to handle (and if possible, the current way of achieving this)
Daily on week... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:1"
] | 439 | en | 0.45 | 2026-09-21T12:13:30.334193Z |
aip-0039-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Proposal | Title: AIP-39: Richer scheduler_interval — Proposal
Proposal: AIP-39 | Project: airflow | State: unknown
## Proposal
### Deprecate execution_date
The name execution_date is just too confusing, and at this point the only practical option is to rename it to something else.
We propose renaming execution_date to data_i... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:2"
] | 872 | en | 0.65 | 2026-09-21T12:13:30.334197Z |
aip-0039-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Example Uses | Title: AIP-39: Richer scheduler_interval — Example Uses
Proposal: AIP-39 | Project: airflow | State: unknown
## Example Uses
A few small illustrative examples of how the given problems outlined at the start can be achieved.
### Use case 1: Daily on weekdays
DataTimetable is for DAGs that have a data interval -- i.e... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:3"
] | 172 | en | 0.45 | 2026-09-21T12:13:30.334200Z |
aip-0039-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Implementation Details | Title: AIP-39: Richer scheduler_interval — Implementation Details
Proposal: AIP-39 | Project: airflow | State: unknown
## Implementation Details
This is not an exhaustive list of steps, just a list of a few salient points.
- Error if scheduler_interval and timetable args both provided to DAG.
- Convert schedule_inte... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:4"
] | 111 | en | 0.35 | 2026-09-21T12:13:30.334203Z |
aip-0039-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087549 | Apache-2.0 | AIP-39: Richer scheduler_interval — Future Enhancements | Title: AIP-39: Richer scheduler_interval — Future Enhancements
Proposal: AIP-39 | Project: airflow | State: unknown
## Future Enhancements
Once we have a basic pluggable timetable/schedule_interval here is some functionality that we could add, either with just a PR, a third party "timetable provider module" or a futu... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:39",
"proposal_state:unknown",
"chunk:5"
] | 474 | en | 0.65 | 2026-09-21T12:13:30.334207Z |
aip-0040-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177050929 | Apache-2.0 | AIP-40: Deferrable ("Async") Operators — Motivation | Title: AIP-40: Deferrable ("Async") Operators — Motivation
Proposal: AIP-40 | Project: airflow | State: unknown
## Motivation
Smart Sensors solve an obvious need - making it a lot less resource-intensive to run many mostly-idle Sensors at once - but they are a relatively limited feature, and not very extensible.
We ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:40",
"proposal_state:unknown",
"chunk:0"
] | 1,336 | en | 0.6 | 2026-09-21T12:13:31.822093Z |
aip-0040-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177050929 | Apache-2.0 | AIP-40: Deferrable ("Async") Operators — Motivation › Which users are affected by the change? | Title: AIP-40: Deferrable ("Async") Operators — Motivation › Which users are affected by the change?
Proposal: AIP-40 | Project: airflow | State: unknown
### Which users are affected by the change?
Users who wish to use deferrable operators will have to run a new process. Nobody else will be affected in the short ter... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:40",
"proposal_state:unknown",
"chunk:2"
] | 125 | en | 0.35 | 2026-09-21T12:13:31.822102Z |
aip-0040-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177050929 | Apache-2.0 | AIP-40: Deferrable ("Async") Operators — Motivation › Other considerations? | Title: AIP-40: Deferrable ("Async") Operators — Motivation › Other considerations?
Proposal: AIP-40 | Project: airflow | State: unknown
### Other considerations?
#### Prototype Implementation
In order to validate the ideas presented, this has already been implemented in a prototype form to ensure all the changes are... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:40",
"proposal_state:unknown",
"chunk:3"
] | 514 | en | 0.475 | 2026-09-21T12:13:31.822106Z |
aip-0042-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191336946 | Apache-2.0 | AIP-42: Dynamic Task Mapping — Processing files in S3 | Title: AIP-42: Dynamic Task Mapping — Processing files in S3
Proposal: AIP-42 | Project: airflow | State: unknown
# Motivation
When writing DAGs in Airflow, users can create arbitrarily parallel tasks in dags at write-time, but not at run-time: users can create thousands of tasks with a single for loop, yet the numbe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:42",
"proposal_state:unknown",
"chunk:0"
] | 298 | en | 0.55 | 2026-09-21T12:13:31.720419Z |
aip-0042-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191336946 | Apache-2.0 | AIP-42: Dynamic Task Mapping — Add `map` and `reduce` functionality to Airflow Operators | Title: AIP-42: Dynamic Task Mapping — Add `map` and `reduce` functionality to Airflow Operators
Proposal: AIP-42 | Project: airflow | State: unknown
## Add `map` and `reduce` functionality to Airflow Operators
For a first-round Dynamic Task creation API, we propose that we start out with the map and reduce functions.... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:42",
"proposal_state:unknown",
"chunk:2"
] | 399 | en | 0.625 | 2026-09-21T12:13:31.720429Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.