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-0089-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Goals | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Goals
Proposal: AIP-89 | Project: airflow | State: unknown
## Goals
**Privacy by design**- Collect only minimal, non-personal data with differential privacy techniques**Transparency**- Users can see exactly what data is collected and sent**User control**- Ea... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:1"
] | 141 | en | 0.375 | 2026-09-21T12:13:29.998993Z |
aip-0089-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data Collected | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data Collected
Proposal: AIP-89 | Project: airflow | State: unknown
### Data Collected
The following minimal data will be collected when telemetry is enabled:
#### Installation Metrics (with noise)
**Airflow version:**Major and minor version inc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:2"
] | 274 | en | 0.45 | 2026-09-21T12:13:29.998997Z |
aip-0089-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data NOT Collected | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data NOT Collected
Proposal: AIP-89 | Project: airflow | State: unknown
### Data NOT Collected
The following data will **explicitly not** be collected:
- DAG names, descriptions, or any DAG content
- Task names, parameters, or configurations
- Va... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:3"
] | 119 | en | 0.35 | 2026-09-21T12:13:29.999000Z |
aip-0089-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Consent Mechanism | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Consent Mechanism
Proposal: AIP-89 | Project: airflow | State: unknown
### Consent Mechanism
#### Default Behavior: Opt-In
Following community feedback from the Scarf incident, telemetry is **opt-in by default**. While this typically yields lower... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:4"
] | 361 | en | 0.525 | 2026-09-21T12:13:29.999003Z |
aip-0089-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Configuration | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Configuration
Proposal: AIP-89 | Project: airflow | State: unknown
### Configuration
#### Database Storage
Telemetry preference is stored in the `airflow_settings` table:
```
INSERT INTO airflow_settings (key, value) VALUES
('telemetry.enable... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:5"
] | 212 | en | 0.525 | 2026-09-21T12:13:29.999007Z |
aip-0089-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data Transmission | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Data Transmission
Proposal: AIP-89 | Project: airflow | State: unknown
### Data Transmission
#### Transmission Schedule
**Frequency:**Once per day (configurable via `collection_interval`)**Time:**Randomized within a 1-hour window to avoid thunder... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:6"
] | 291 | en | 0.55 | 2026-09-21T12:13:29.999010Z |
aip-0089-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Transparency Features | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Transparency Features
Proposal: AIP-89 | Project: airflow | State: unknown
### Transparency Features
#### Debug Mode
Users can inspect telemetry data before it's sent:
```
# See exactly what would be sent (without actually sending)
$ airflow tel... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:7"
] | 122 | en | 0.425 | 2026-09-21T12:13:29.999013Z |
aip-0089-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Governance and Changes | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Proposal › Governance and Changes
Proposal: AIP-89 | Project: airflow | State: unknown
### Governance and Changes
#### Process for Modifying Collected Data
Any changes to the data collected (additions or removals) require:
**Discussion on Dev List:**Propos... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:8"
] | 153 | en | 0.35 | 2026-09-21T12:13:29.999016Z |
aip-0089-13 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Alternatives Considered | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Alternatives Considered
Proposal: AIP-89 | Project: airflow | State: unknown
## Alternatives Considered
### Alternative 1: No Telemetry
**Rationale for rejection:** Development prioritization would rely solely on GitHub issues and surveys, which don't repre... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:13"
] | 232 | en | 0.425 | 2026-09-21T12:13:29.999032Z |
aip-0089-14 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Addressing Common Concerns | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Addressing Common Concerns
Proposal: AIP-89 | Project: airflow | State: unknown
## Addressing Common Concerns
### "Why not make it opt-out?"
Given typical opt-in participation rates of 3-10%, opt-out would give us much better data coverage. However, after t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:14"
] | 227 | en | 0.425 | 2026-09-21T12:13:29.999035Z |
aip-0089-15 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=340036477 | Apache-2.0 | AIP-89: Privacy-First Telemetry for Apache Airflow — Risks and Mitigations | Title: AIP-89: Privacy-First Telemetry for Apache Airflow — Risks and Mitigations
Proposal: AIP-89 | Project: airflow | State: unknown
## Risks and Mitigations
Risk | Mitigation |
---|---|
Low adoption rate | Accept 5-10% participation as cost of trust-building; supplement with targeted surveys and optional "extende... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:89",
"proposal_state:unknown",
"chunk:15"
] | 171 | en | 0.35 | 2026-09-21T12:13:29.999038Z |
aip-0090-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=362056119 | Apache-2.0 | AIP-90: Human in the loop — Motivation | Title: AIP-90: Human in the loop — Motivation
Proposal: AIP-90 | Project: airflow | State: unknown
## Motivation
As we have been having conversations with Airflow users, who are using Airflow for Gen AI applications, there are a couple of features that have been brought up as being desirable. As context, based on the... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:90",
"proposal_state:unknown",
"chunk:0"
] | 323 | en | 0.475 | 2026-09-21T12:13:28.949324Z |
aip-0090-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=362056119 | Apache-2.0 | AIP-90: Human in the loop — Considerations | Title: AIP-90: Human in the loop — Considerations
Proposal: AIP-90 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
At a high level, we propose to make the following changes:
- Introduce a set of "human operators" corresponding to the flows described above. These "human ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:90",
"proposal_state:unknown",
"chunk:1"
] | 1,447 | en | 0.5 | 2026-09-21T12:13:28.949330Z |
aip-0091-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=364349979 | Apache-2.0 | AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Motivation | Title: AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Motivation
Proposal: AIP-91 | Project: airflow | State: unknown
## Motivation
Model Context Protocol (MCP) is an open standard, open-source framework that standardizes the way AI models like LLM integrate and share data with external tools, systems and... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:91",
"proposal_state:unknown",
"chunk:0"
] | 308 | en | 0.475 | 2026-09-21T12:13:28.912684Z |
aip-0091-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=364349979 | Apache-2.0 | AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Proposed Solution & Architecture | Title: AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Proposed Solution & Architecture
Proposal: AIP-91 | Project: airflow | State: unknown
## Proposed Solution & Architecture
To satisfy the strict security and operational requirements of the Airflow AI Assistant (AIP-101) and other external integrations,... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:91",
"proposal_state:unknown",
"chunk:1"
] | 473 | en | 0.5 | 2026-09-21T12:13:28.912690Z |
aip-0091-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=364349979 | Apache-2.0 | AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Security Model & Controls | Title: AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Security Model & Controls
Proposal: AIP-91 | Project: airflow | State: unknown
## Security Model & Controls
Because the MCP Server exposes Airflow's operational state to non-deterministic external LLMs, it requires stringent, defense-in-depth security ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:91",
"proposal_state:unknown",
"chunk:2"
] | 384 | en | 0.425 | 2026-09-21T12:13:28.912694Z |
aip-0091-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=364349979 | Apache-2.0 | AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Considerations | Title: AIP-91: Airflow MCP Server (Phase 1 - Read-only actions) — Considerations
Proposal: AIP-91 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
We propose to implement an official **Model Context Protocol (MCP) server **for Apache Airflow.
**Standalone Release within ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:91",
"proposal_state:unknown",
"chunk:3"
] | 789 | en | 0.475 | 2026-09-21T12:13:28.912697Z |
aip-0092-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886718 | Apache-2.0 | AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Motivation | Title: AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Motivation
Proposal: AIP-92 | Project: airflow | State: unknown
## Motivation
### What problem does it solve? / Why is it needed?
With Airflow 3, task execution got separated from Core Airflow services and lost direct access... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:92",
"proposal_state:unknown",
"chunk:0"
] | 563 | en | 0.45 | 2026-09-21T12:13:34.112848Z |
aip-0092-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886718 | Apache-2.0 | AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Considerations | Title: AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Considerations
Proposal: AIP-92 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
#### Phase 1
From the very beginning Airflow relied on DAG parsing loop continuously re-parsing a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:92",
"proposal_state:unknown",
"chunk:1"
] | 484 | en | 0.5 | 2026-09-21T12:13:34.112857Z |
aip-0092-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886718 | Apache-2.0 | AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Phase 2 | Title: AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Phase 2
Proposal: AIP-92 | Project: airflow | State: unknown
## Phase 2
Callbacks are primarily of two types, DagCallbackRequests and TaskCallbackRequests. These callbacks get stored into the DB in table named "callback_reque... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:92",
"proposal_state:unknown",
"chunk:2"
] | 324 | en | 0.55 | 2026-09-21T12:13:34.112861Z |
aip-0092-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886718 | Apache-2.0 | AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Phase 3 | Title: AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Phase 3
Proposal: AIP-92 | Project: airflow | State: unknown
## Phase 3
In the final phase, we would be targeting Triggerer svc to not using direct DB operations and instead go through via API route. As of now, Triggerer make... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:92",
"proposal_state:unknown",
"chunk:3"
] | 118 | en | 0.35 | 2026-09-21T12:13:34.112864Z |
aip-0092-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886718 | Apache-2.0 | AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Path to implementation | Title: AIP-92: Isolate DAG processor, Callback processor, and Triggerer from core services — Path to implementation
Proposal: AIP-92 | Project: airflow | State: unknown
## Path to implementation
The implementation for Phase 1 would be rather simple and will be behind a flag, which would control whether to use the cur... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:92",
"proposal_state:unknown",
"chunk:4"
] | 1,357 | en | 0.55 | 2026-09-21T12:13:34.112869Z |
aip-0093-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886908 | Apache-2.0 | AIP-93: Asset Watermarks — Motivation | Title: AIP-93: Asset Watermarks — Motivation
Proposal: AIP-93 | Project: airflow | State: unknown
## Motivation
Incremental processing is one of the most, it not *the* most common pattern implement with Airflow. Although external event driven scheduling is supported today in Airflow via AIP-82, incremental polling is... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:93",
"proposal_state:unknown",
"chunk:1"
] | 222 | en | 0.55 | 2026-09-21T12:13:27.006216Z |
aip-0093-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=373886908 | Apache-2.0 | AIP-93: Asset Watermarks — Considerations | Title: AIP-93: Asset Watermarks — Considerations
Proposal: AIP-93 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
At a high level, we propose to make the following changes:
- Pass through context including the Asset being "watched" to the `BaseEventTrigger` to make the ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:93",
"proposal_state:unknown",
"chunk:2"
] | 899 | en | 0.725 | 2026-09-21T12:13:27.006223Z |
aip-0094-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=382175838 | Apache-2.0 | AIP-94: Decouple Remote Commands from airflow CLI (to airflowctl) — Considerations | Title: AIP-94: Decouple Remote Commands from airflow CLI (to airflowctl) — Considerations
Proposal: AIP-94 | Project: airflow | State: unknown
## Considerations
At a high level:
- Limit the development of airflow CLI commands for Remote commands.
- Deprecate airflow CLI commands that overlap with airflowctl.
- Provi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:94",
"proposal_state:unknown",
"chunk:1"
] | 745 | en | 0.425 | 2026-09-21T12:13:29.930772Z |
aip-0095-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Motivation | Title: AIP-95: Provider lifecycle update proposal — Motivation
Proposal: AIP-95 | Project: airflow | State: unknown
## Motivation
A key set of capabilities which has made Airflow successful has been its large set of community supported integrations which number over 1,600 (hooks, operators, and sensors), released as ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:0"
] | 233 | en | 0.5 | 2026-09-21T12:13:28.827371Z |
aip-0095-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance | Title: AIP-95: Provider lifecycle update proposal — Updated Governance
Proposal: AIP-95 | Project: airflow | State: unknown
## Updated Governance
This proposal follows the three stage (Incubation, Production, and Deprecation) policy, but establishes stronger procedures, metrics, and communication around these, for mo... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:1"
] | 277 | en | 0.45 | 2026-09-21T12:13:28.827377Z |
aip-0095-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Incubation | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Incubation
Proposal: AIP-95 | Project: airflow | State: unknown
### Incubation
All new providers or other integration modules (such as Notifiers, Message components, etc.) should start in incubation (unless specifically accelerated by the PMC) t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:2"
] | 415 | en | 0.475 | 2026-09-21T12:13:28.827380Z |
aip-0095-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Attic / Deprecation | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Attic / Deprecation
Proposal: AIP-95 | Project: airflow | State: unknown
### Attic / Deprecation
Modules should be moved into the Attic when relevance wanes, usually measured by activity. Typically this is because the solution to be integrated h... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:3"
] | 237 | en | 0.45 | 2026-09-21T12:13:28.827384Z |
aip-0095-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Repository | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Repository
Proposal: AIP-95 | Project: airflow | State: unknown
### Repository
Move all the community providers and integrations into a separate repo from Core Airflow, but within the overall Airflow project.
This specifically excludes the foll... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:5"
] | 164 | en | 0.375 | 2026-09-21T12:13:28.827390Z |
aip-0095-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Consistency | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Consistency
Proposal: AIP-95 | Project: airflow | State: unknown
### Consistency
We should double down on the "common" patterns for integration for consistency of DAG author development as well as ease of maintenance and testing.
AI assisted to... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:6"
] | 115 | en | 0.375 | 2026-09-21T12:13:28.827393Z |
aip-0095-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Distribution | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Distribution
Proposal: AIP-95 | Project: airflow | State: unknown
### Distribution
We suggest a simple evolution of the existing Provider release process here, since these providers are outside of core Airflow and in a separate repo.
It is feas... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:7"
] | 156 | en | 0.35 | 2026-09-21T12:13:28.827396Z |
aip-0095-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=383191675 | Apache-2.0 | AIP-95: Provider lifecycle update proposal — Updated Governance › Discovery | Title: AIP-95: Provider lifecycle update proposal — Updated Governance › Discovery
Proposal: AIP-95 | Project: airflow | State: unknown
### Discovery
One of the key reasons for people wanting to contribute integrations into the "Airflow repo" is discovery. Not only should we encourage this in the form of a "Airflow i... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:95",
"proposal_state:unknown",
"chunk:8"
] | 117 | en | 0.35 | 2026-09-21T12:13:28.827399Z |
aip-0096-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279303 | Apache-2.0 | AIP-96: Resumable Operators — Motivation | Title: AIP-96: Resumable Operators — Motivation
Proposal: AIP-96 | Project: airflow | State: unknown
## Motivation
## Summary
This AIP proposes adding **reconnection/resumption** capability to operators that submit long-running external jobs (Databricks, EMR, Snowflake, dbt Cloud, etc.). When infrastructure disrupti... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:96",
"proposal_state:unknown",
"chunk:0"
] | 110 | en | 0.375 | 2026-09-21T12:13:27.439137Z |
aip-0096-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279303 | Apache-2.0 | AIP-96: Resumable Operators — Motivation | Title: AIP-96: Resumable Operators — Motivation
Proposal: AIP-96 | Project: airflow | State: unknown
## Motivation
### Current Behavior and Limitations
**Problem: Wasted Computation from Infrastructure Disruptions**
When operators submit long-running external jobs and monitor their completion, infrastructure disrup... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:96",
"proposal_state:unknown",
"chunk:1"
] | 140 | en | 0.35 | 2026-09-21T12:13:27.439144Z |
aip-0096-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279303 | Apache-2.0 | AIP-96: Resumable Operators — Considerations | Title: AIP-96: Resumable Operators — Considerations
Proposal: AIP-96 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
### Problem Visualization
**Current Behavior (Wasteful):**
**Proposed Behavior (Resumable):**
### Core Concept
Extend the existing **deferral pattern*... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:96",
"proposal_state:unknown",
"chunk:2"
] | 1,089 | en | 0.55 | 2026-09-21T12:13:27.439148Z |
aip-0097-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279312 | Apache-2.0 | AIP-97: Task Failure Classification — Proposal | Title: AIP-97: Task Failure Classification — Proposal
Proposal: AIP-97 | Project: airflow | State: draft
## Proposal
### Failure cause contract
The optional, typed `failure_kind` identifies a broad category. The optional `reason` carries a short diagnostic value, such as a backend reason code. Workers supply causes ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:97",
"proposal_state:draft",
"chunk:1"
] | 461 | en | 0.45 | 2026-09-21T12:13:27.017744Z |
aip-0097-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279312 | Apache-2.0 | AIP-97: Task Failure Classification — Compatibility and scope | Title: AIP-97: Task Failure Classification — Compatibility and scope
Proposal: AIP-97 | Project: airflow | State: draft
## Compatibility and scope
Executors that omit the cause fields keep their existing failure behavior. Providers can adopt the contract independently as their backends offer reliable signals; absence... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:97",
"proposal_state:draft",
"chunk:2"
] | 194 | en | 0.425 | 2026-09-21T12:13:27.017749Z |
aip-0097-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279312 | Apache-2.0 | AIP-97: Task Failure Classification — Implementation and acceptance | Title: AIP-97: Task Failure Classification — Implementation and acceptance
Proposal: AIP-97 | Project: airflow | State: draft
## Implementation and acceptance
The classification implementation is independently reviewable at 6edb01f. It contains failure reporting without retry configuration, replacement accounting or ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:97",
"proposal_state:draft",
"chunk:4"
] | 264 | en | 0.45 | 2026-09-21T12:13:27.017757Z |
aip-0098-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279574 | Apache-2.0 | AIP-98: Add async support for PythonOperator in Airflow 3 — Motivation | Title: AIP-98: Add async support for PythonOperator in Airflow 3 — Motivation
Proposal: AIP-98 | Project: airflow | State: unknown
## Motivation
At our company, we strive to avoid custom code in Airflow as much as possible to improve maintainability. For years this meant favouring dedicated Airflow operators over Pyt... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:98",
"proposal_state:unknown",
"chunk:0"
] | 1,515 | en | 0.575 | 2026-09-21T12:13:29.965666Z |
aip-0098-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=399279574 | Apache-2.0 | AIP-98: Add async support for PythonOperator in Airflow 3 — Considerations | Title: AIP-98: Add async support for PythonOperator in Airflow 3 — Considerations
Proposal: AIP-98 | Project: airflow | State: unknown
## Considerations
In my opinion there are no special considerations to be made, except the new functionality (e.g. supporting async code natively in PythonOperator) will only be avail... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:98",
"proposal_state:unknown",
"chunk:1"
] | 226 | en | 0.45 | 2026-09-21T12:13:29.965672Z |
aip-0099-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618285 | Apache-2.0 | AIP-99: Common Data Access Pattern + AI — Background & Motivation | Title: AIP-99: Common Data Access Pattern + AI — Background & Motivation
Proposal: AIP-99 | Project: airflow | State: unknown
## Background & Motivation
In today's evolving data landscape, organizations face significant challenges:
**Schema Drift Detection**: Breaking changes between upstream and downstream systems ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:99",
"proposal_state:unknown",
"chunk:0"
] | 154 | en | 0.475 | 2026-09-21T12:13:28.807109Z |
aip-0099-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618285 | Apache-2.0 | AIP-99: Common Data Access Pattern + AI — Core Proposal: Specialized LLM Operators with Rich Context Integration | Title: AIP-99: Common Data Access Pattern + AI — Core Proposal: Specialized LLM Operators with Rich Context Integration
Proposal: AIP-99 | Project: airflow | State: unknown
## Core Proposal: Specialized LLM Operators with Rich Context Integration
Based on Pydantic AI's capabilities, while it provides excellent agent ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:99",
"proposal_state:unknown",
"chunk:1"
] | 541 | en | 0.625 | 2026-09-21T12:13:28.807116Z |
aip-0099-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618285 | Apache-2.0 | AIP-99: Common Data Access Pattern + AI — Complete Workflow Example | Title: AIP-99: Common Data Access Pattern + AI — Complete Workflow Example
Proposal: AIP-99 | Project: airflow | State: unknown
## Complete Workflow Example
Here's a real-world scenario combining all components:
## Evolution Path: From LLMOperator to AITask
While we start with SQL generation, the architecture suppo... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:99",
"proposal_state:unknown",
"chunk:2"
] | 472 | en | 0.625 | 2026-09-21T12:13:28.807120Z |
aip-0099-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618285 | Apache-2.0 | AIP-99: Common Data Access Pattern + AI — Why This Matters | Title: AIP-99: Common Data Access Pattern + AI — Why This Matters
Proposal: AIP-99 | Project: airflow | State: unknown
## Why This Matters
**For Airflow**:
- Positions Airflow at the center of AI-powered data infrastructure
**Makes Airflow more data-aware**: Enhanced Asset metadata creates richer data context and li... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:99",
"proposal_state:unknown",
"chunk:3"
] | 212 | en | 0.475 | 2026-09-21T12:13:28.807124Z |
aip-0100-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits
Proposal: AIP-100 | Project: airflow | State: unknown
**Motivation**
The critical section in Airflow's scheduler uses an optimistic strategy: it fetches a batch of scheduled task instances from the database (up to `max_tis_per_query`), then... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:0"
] | 585 | en | 0.425 | 2026-09-21T12:13:28.892513Z |
aip-0100-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — What change do you propose to make? | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — What change do you propose to make?
Proposal: AIP-100 | Project: airflow | State: unknown
## What change do you propose to make?
Change the methodology in which the scheduler currently decides which tasks to run, allowing for an increased... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:1"
] | 281 | en | 0.45 | 2026-09-21T12:13:28.892521Z |
aip-0100-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Why is it needed? | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Why is it needed?
Proposal: AIP-100 | Project: airflow | State: unknown
## Why is it needed?
Large-scale Airflow deployments with dynamic task mapping—generating thousands of tasks per DAG—suffer severe scheduler starvation. The optimisti... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:2"
] | 274 | en | 0.475 | 2026-09-21T12:13:28.892525Z |
aip-0100-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — How is the airflow scheduler different? | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — How is the airflow scheduler different?
Proposal: AIP-100 | Project: airflow | State: unknown
## How is the airflow scheduler different?
Many of the studied and optimized schedulers (along with the algorithms) mainly refer to schedulers w... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:4"
] | 300 | en | 0.425 | 2026-09-21T12:13:28.892531Z |
aip-0100-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Which users are affected by the change? | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Which users are affected by the change?
Proposal: AIP-100 | Project: airflow | State: unknown
## Which users are affected by the change?
- Large-scale deployments
- Deployments shared by several teams
- Power users - clients that heavily ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:5"
] | 158 | en | 0.4 | 2026-09-21T12:13:28.892534Z |
aip-0100-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Implementation Considerations | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Implementation Considerations
Proposal: AIP-100 | Project: airflow | State: unknown
## Implementation Considerations
### Priority Semantics Changes
A consensus within the community suggests that rethinking priorities is a viable option a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:6"
] | 815 | en | 0.475 | 2026-09-21T12:13:28.892538Z |
aip-0100-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies
Proposal: AIP-100 | Project: airflow | State: unknown
## Proposed Priority Strategies
As we approached on a solution, we decided to move on with changing the priorities in airflow, we have a few possible strat... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:7"
] | 111 | en | 0.35 | 2026-09-21T12:13:28.892541Z |
aip-0100-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Keeping task-level priorities but making them weaker | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Keeping task-level priorities but making them weaker
Proposal: AIP-100 | Project: airflow | State: unknown
### Keeping task-level priorities but making them weaker
Retain task-level priority weights, but mak... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:8"
] | 344 | en | 0.475 | 2026-09-21T12:13:28.892544Z |
aip-0100-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Introducing DAG-level priorities, changing task-level priorities | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Introducing DAG-level priorities, changing task-level priorities
Proposal: AIP-100 | Project: airflow | State: unknown
### Introducing DAG-level priorities, changing task-level priorities
Introduce DAG-level... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:9"
] | 358 | en | 0.45 | 2026-09-21T12:13:28.892547Z |
aip-0100-10 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Introducing DAG-level priorities, giving up task-level priorities | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Introducing DAG-level priorities, giving up task-level priorities
Proposal: AIP-100 | Project: airflow | State: unknown
### Introducing DAG-level priorities, giving up task-level priorities
The approach sugg... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:10"
] | 331 | en | 0.45 | 2026-09-21T12:13:28.892550Z |
aip-0100-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Completely removing all priorities at all levels | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Completely removing all priorities at all levels
Proposal: AIP-100 | Project: airflow | State: unknown
### Completely removing all priorities at all levels
Suggests to remove all priorities, use plain round-... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:11"
] | 338 | en | 0.45 | 2026-09-21T12:13:28.892554Z |
aip-0100-12 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Proposed Obsolescence Algorithms | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Proposed Obsolescence Algorithms
Proposal: AIP-100 | Project: airflow | State: unknown
### Proposed Obsolescence Algorithms
#### Obsolescence Algorithm
Implementing any change in the priority semantics stil... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:12"
] | 948 | en | 0.45 | 2026-09-21T12:13:28.892557Z |
aip-0100-13 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Current best proposition | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Proposed Priority Strategies › Current best proposition
Proposal: AIP-100 | Project: airflow | State: unknown
### Current best proposition
As of now, the best proposition is to have an algorith like the one described here, where we have 3... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:13"
] | 472 | en | 0.425 | 2026-09-21T12:13:28.892561Z |
aip-0100-14 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — What defines this AIP as "done"? | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — What defines this AIP as "done"?
Proposal: AIP-100 | Project: airflow | State: unknown
## What defines this AIP as "done"?
The Airflow scheduler's performance improves in terms of queued tasks over a time frame. Any unnecessary starvation... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:14"
] | 778 | en | 0.45 | 2026-09-21T12:13:28.892564Z |
aip-0100-15 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406618462 | Apache-2.0 | AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Alternatives considered | Title: AIP-100: Eliminate Scheduler Queueing Starvation On Concurrency Limits — Alternatives considered
Proposal: AIP-100 | Project: airflow | State: unknown
## Alternatives considered
Strategy |
| Single-limit pre-filtering | Window functions | SQL procedures / exhaustive linear scan |
|
Description | Fetch up to `... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:100",
"proposal_state:unknown",
"chunk:15"
] | 785 | en | 0.5 | 2026-09-21T12:13:28.892567Z |
aip-0101-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406620144 | Apache-2.0 | AIP-101: Airflow AI Assistant — Motivation | Title: AIP-101: Airflow AI Assistant — Motivation
Proposal: AIP-101 | Project: airflow | State: unknown
## Motivation
Airflow, as a leading open-source platform for data engineering and orchestration, sits at the center of many production data platforms, coordinating critical pipelines, integrations, and cross-team d... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:101",
"proposal_state:unknown",
"chunk:0"
] | 213 | en | 0.5 | 2026-09-21T12:13:28.769457Z |
aip-0101-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406620144 | Apache-2.0 | AIP-101: Airflow AI Assistant — Considerations | Title: AIP-101: Airflow AI Assistant — Considerations
Proposal: AIP-101 | Project: airflow | State: unknown
## Considerations
This proposal introduces a new integration surface between Airflow and external AI systems, expanding the system's security and operational surface.
Key considerations include:
**Security su... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:101",
"proposal_state:unknown",
"chunk:1"
] | 1,145 | en | 0.45 | 2026-09-21T12:13:28.769463Z |
aip-0102-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623093 | Apache-2.0 | AIP-102: Improving Business User Interaction with Apache Airflow | Title: AIP-102: Improving Business User Interaction with Apache Airflow
Proposal: AIP-102 | Project: airflow | State: unknown
Motivation
Airflow is driven by data engineers and technology, thus tasks and results are viewed on a technical level. If something goes wrong users need to check logs in the UI. Since Airflow... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:102",
"proposal_state:unknown",
"chunk:0"
] | 361 | en | 0.4 | 2026-09-21T12:13:28.932645Z |
aip-0102-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623093 | Apache-2.0 | AIP-102: Improving Business User Interaction with Apache Airflow — Considerations | Title: AIP-102: Improving Business User Interaction with Apache Airflow — Considerations
Proposal: AIP-102 | Project: airflow | State: unknown
## Considerations
We propose to add an optional feature allowing to expose a good human readable Dag Run and Task Instance Summary via Markdown Templates. We envision this is ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:102",
"proposal_state:unknown",
"chunk:1"
] | 1,513 | en | 0.45 | 2026-09-21T12:13:28.932652Z |
aip-0103-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623137 | Apache-2.0 | AIP-103: Task State Management — Motivation | Title: AIP-103: Task State Management — Motivation
Proposal: AIP-103 | Project: airflow | State: unknown
## Motivation
Apache Airflow has always treated tasks as stateless, idempotent units of work. This design philosophy has served the project well and remains the right default for the vast majority of use cases. Ho... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:103",
"proposal_state:unknown",
"chunk:0"
] | 1,277 | en | 0.7 | 2026-09-21T12:13:27.481682Z |
aip-0103-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623137 | Apache-2.0 | AIP-103: Task State Management — Considerations › What change do you propose to make? | Title: AIP-103: Task State Management — Considerations › What change do you propose to make?
Proposal: AIP-103 | Project: airflow | State: unknown
### What change do you propose to make?
At a high level, this AIP proposes the following changes:
- Introduce a Task State data model supporting two distinct scoping mode... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:103",
"proposal_state:unknown",
"chunk:1"
] | 1,433 | en | 0.7 | 2026-09-21T12:13:27.481687Z |
aip-0103-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623137 | Apache-2.0 | AIP-103: Task State Management — Considerations › Which users are affected by the change? | Title: AIP-103: Task State Management — Considerations › Which users are affected by the change?
Proposal: AIP-103 | Project: airflow | State: unknown
### Which users are affected by the change?
This change is purely additive and non-breaking. No existing user is required to change any DAG code or deployment configur... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:103",
"proposal_state:unknown",
"chunk:2"
] | 153 | en | 0.4 | 2026-09-21T12:13:27.481691Z |
aip-0103-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623137 | Apache-2.0 | AIP-103: Task State Management — Considerations › How are users affected by the change? (e.g. DB upgrade required?) | Title: AIP-103: Task State Management — Considerations › How are users affected by the change? (e.g. DB upgrade required?)
Proposal: AIP-103 | Project: airflow | State: unknown
### How are users affected by the change? (e.g. DB upgrade required?)
A database migration is required to add the task_state table to the Air... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:103",
"proposal_state:unknown",
"chunk:3"
] | 611 | en | 0.5 | 2026-09-21T12:13:27.481694Z |
aip-0104-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421954527 | Apache-2.0 | AIP-104: Iterable Tasks (IT) and Batched Task Mapping. (BTM) | Title: AIP-104: Iterable Tasks (IT) and Batched Task Mapping. (BTM)
Proposal: AIP-104 | Project: airflow | State: unknown
Motivation
Airflow's existing **Dynamic Task Mapping (DTM)** provides a powerful way to process collections by expanding tasks into multiple Task Instances. However, this model introduces signific... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:104",
"proposal_state:unknown",
"chunk:0"
] | 235 | en | 0.375 | 2026-09-21T12:13:27.193667Z |
aip-0104-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421954527 | Apache-2.0 | AIP-104: Iterable Tasks (IT) and Batched Task Mapping. (BTM) — Considerations | Title: AIP-104: Iterable Tasks (IT) and Batched Task Mapping. (BTM) — Considerations
Proposal: AIP-104 | Project: airflow | State: unknown
## Considerations
Iterable Tasks introduces a fundamentally different execution model compared to Dynamic Task Mapping (DTM), which leads to several trade-offs and behavioural dif... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:104",
"proposal_state:unknown",
"chunk:1"
] | 1,491 | en | 0.6 | 2026-09-21T12:13:27.193675Z |
aip-0105-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — How the pieces fit together | Title: AIP-105: Pluggable Retry Policies — How the pieces fit together
Proposal: AIP-105 | Project: airflow | State: unknown
## How the pieces fit together
A retry policy is an object you attach to a task with `retry_policy=...`. When the task **fails**, the policy's `evaluate(exception, try_number, max_tries, contex... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:1"
] | 402 | en | 0.55 | 2026-09-21T12:13:27.606427Z |
aip-0105-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 1. Migration testing | Title: AIP-105: Pluggable Retry Policies — 1. Migration testing
Proposal: AIP-105 | Project: airflow | State: unknown
## 1. Migration testing
Migration `0113_3_3_0_add_retry_policy_fields_to_ti.py` (revision `b8f3e4a1d2c9`, down-revision `fde9ed84d07b`) adds two **nullable** columns — `retry_delay_override` (Float) a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:2"
] | 332 | en | 0.425 | 2026-09-21T12:13:27.606431Z |
aip-0105-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 2. Functional — `ExceptionRetryPolicy` (declarative backend) | Title: AIP-105: Pluggable Retry Policies — 2. Functional — `ExceptionRetryPolicy` (declarative backend)
Proposal: AIP-105 | Project: airflow | State: unknown
## 2. Functional — `ExceptionRetryPolicy` (declarative backend)
Full-stack via a running worker. Trigger `aip105_retry_policy_qa` (reference DAG above) unless n... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:3"
] | 573 | en | 0.45 | 2026-09-21T12:13:27.606434Z |
aip-0105-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 3. Functional — fail-fast exceptions that bypass the policy | Title: AIP-105: Pluggable Retry Policies — 3. Functional — fail-fast exceptions that bypass the policy
Proposal: AIP-105 | Project: airflow | State: unknown
## 3. Functional — fail-fast exceptions that bypass the policy
The policy is consulted for `AirflowException`, `AirflowTaskTimeout`, `AirflowRuntimeError`, `Syst... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:4"
] | 212 | en | 0.425 | 2026-09-21T12:13:27.606437Z |
aip-0105-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 4. Delay-override & reason persistence lifecycle | Title: AIP-105: Pluggable Retry Policies — 4. Delay-override & reason persistence lifecycle
Proposal: AIP-105 | Project: airflow | State: unknown
## 4. Delay-override & reason persistence lifecycle
ID | Test Case | Expected Result | Pass Criteria | Execution Result |
---|---|---|---|---|
L-01 `[P0]` `[DB required]` ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:5"
] | 216 | en | 0.425 | 2026-09-21T12:13:27.606440Z |
aip-0105-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 6. Serialization | Title: AIP-105: Pluggable Retry Policies — 6. Serialization
Proposal: AIP-105 | Project: airflow | State: unknown
## 6. Serialization
The policy object is **not** serialized; only `has_retry_policy: bool` is stored. The worker re-parses the DAG to obtain the live policy.
ID | Test Case | Expected Result | Pass Crite... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:7"
] | 206 | en | 0.475 | 2026-09-21T12:13:27.606446Z |
aip-0105-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 7. LLM backend — `LLMRetryPolicy` (`apache-airflow-providers-common-ai`) | Title: AIP-105: Pluggable Retry Policies — 7. LLM backend — `LLMRetryPolicy` (`apache-airflow-providers-common-ai`)
Proposal: AIP-105 | Project: airflow | State: unknown
## 7. LLM backend — `LLMRetryPolicy` (`apache-airflow-providers-common-ai`)
Requires Airflow 3.3+ and `apache-airflow-providers-common-ai[<llm-extra... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:8"
] | 567 | en | 0.45 | 2026-09-21T12:13:27.606449Z |
aip-0105-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 8. Cadwyn / API version compatibility | Title: AIP-105: Pluggable Retry Policies — 8. Cadwyn / API version compatibility
Proposal: AIP-105 | Project: airflow | State: unknown
## 8. Cadwyn / API version compatibility
Execution-API version `v2026_06_16` (`AddRetryPolicyFields`) adds `retry_delay_seconds` and `retry_reason` to `TIRetryStatePayload`.
ID | Tes... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:9"
] | 352 | en | 0.475 | 2026-09-21T12:13:27.606452Z |
aip-0105-10 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 9. Safety / negative cases | Title: AIP-105: Pluggable Retry Policies — 9. Safety / negative cases
Proposal: AIP-105 | Project: airflow | State: unknown
## 9. Safety / negative cases
ID | Test Case | Expected Result | Pass Criteria | Execution Result |
---|---|---|---|---|
N-01 `[P0]` | Scheduler never instantiates or runs the policy | Parse a ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:10"
] | 166 | en | 0.35 | 2026-09-21T12:13:27.606455Z |
aip-0105-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430409279 | Apache-2.0 | AIP-105: Pluggable Retry Policies — 10. Documentation review | Title: AIP-105: Pluggable Retry Policies — 10. Documentation review
Proposal: AIP-105 | Project: airflow | State: unknown
## 10. Documentation review
ID | Test Case | Pass Criteria | Execution Result |
---|---|---|---|
D-01 `[P1]` | Core docs cover the feature | `airflow-core/docs/core-concepts/tasks.rst` documents ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:105",
"proposal_state:unknown",
"chunk:11"
] | 106 | en | 0.35 | 2026-09-21T12:13:27.606458Z |
aip-0106-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Motivation | Title: AIP-106: Composable Trigger Rules — Motivation
Proposal: AIP-106 | Project: airflow | State: unknown
## Motivation
Real-world pipelines rarely fit a clean "all-or-nothing" dependency model. A few recurring shapes that Airflow users encounter every day:
**Fan-out data ingestion.**A team ingests partitioned dat... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:0"
] | 546 | en | 0.5 | 2026-09-21T12:13:28.752791Z |
aip-0106-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations | Title: AIP-106: Composable Trigger Rules — Considerations
Proposal: AIP-106 | Project: airflow | State: unknown
## Considerations
**No change to failure semantics.**Every existing enum value that has an
expression equivalent must produce the same result under that expression for
every upstream-state vector: same pa... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:1"
] | 181 | en | 0.4 | 2026-09-21T12:13:28.752798Z |
aip-0106-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations › What change do you propose to make? | Title: AIP-106: Composable Trigger Rules — Considerations › What change do you propose to make?
Proposal: AIP-106 | Project: airflow | State: unknown
### What change do you propose to make?
Add a structured expression form for trigger rules that lives alongside the existing enum.
```py
from airflow.sdk import Trigge... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:2"
] | 716 | en | 0.525 | 2026-09-21T12:13:28.752803Z |
aip-0106-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations › What problem does it solve? | Title: AIP-106: Composable Trigger Rules — Considerations › What problem does it solve?
Proposal: AIP-106 | Project: airflow | State: unknown
### What problem does it solve?
Authors today express dependency conditions by picking from a hard-coded list of 13 presets. When the one they need is not there, the options ar... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:3"
] | 213 | en | 0.475 | 2026-09-21T12:13:28.752806Z |
aip-0106-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations › Are there any downsides to this change? | Title: AIP-106: Composable Trigger Rules — Considerations › Are there any downsides to this change?
Proposal: AIP-106 | Project: airflow | State: unknown
### Are there any downsides to this change?
**More surface area to document -**The expression form has its own small grammar. The docs need a clear mapping table an... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:5"
] | 167 | en | 0.35 | 2026-09-21T12:13:28.752812Z |
aip-0106-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations › How are users affected by the change? (e.g. DB upgrade required?) | Title: AIP-106: Composable Trigger Rules — Considerations › How are users affected by the change? (e.g. DB upgrade required?)
Proposal: AIP-106 | Project: airflow | State: unknown
### How are users affected by the change? (e.g. DB upgrade required?)
**No DB migration**- Trigger rules live in serialized Dag JSON, whic... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:6"
] | 282 | en | 0.45 | 2026-09-21T12:13:28.752815Z |
aip-0106-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421956843 | Apache-2.0 | AIP-106: Composable Trigger Rules — Considerations › What defines this AIP as "done"? | Title: AIP-106: Composable Trigger Rules — Considerations › What defines this AIP as "done"?
Proposal: AIP-106 | Project: airflow | State: unknown
### What defines this AIP as "done"?
• The expression form is available in the Task SDK, documented with the mapping
table, and has at least one example Dag in `example_d... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:106",
"proposal_state:unknown",
"chunk:7"
] | 456 | en | 0.45 | 2026-09-21T12:13:28.752819Z |
aip-0107-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421957237 | Apache-2.0 | AIP-107: Direct Queueing from Triggerer - or other means to prevent Latency for Tasks exiting deferred State — Motivation | Title: AIP-107: Direct Queueing from Triggerer - or other means to prevent Latency for Tasks exiting deferred State — Motivation
Proposal: AIP-107 | Project: airflow | State: unknown
## Motivation
**TLDR: **Because of operational problems in processing workload we propose an extension allowing to directly re-queue ta... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:107",
"proposal_state:unknown",
"chunk:0"
] | 1,207 | en | 0.475 | 2026-09-21T12:13:29.003745Z |
aip-0107-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421957237 | Apache-2.0 | AIP-107: Direct Queueing from Triggerer - or other means to prevent Latency for Tasks exiting deferred State — Considerations | Title: AIP-107: Direct Queueing from Triggerer - or other means to prevent Latency for Tasks exiting deferred State — Considerations
Proposal: AIP-107 | Project: airflow | State: unknown
## Considerations
The following options were considered:
- Proposing a new "state" for a task instance, e.g. "re-schedule" that is... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:107",
"proposal_state:unknown",
"chunk:1"
] | 1,482 | en | 0.5 | 2026-09-21T12:13:29.003752Z |
aip-0108-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 | Title: AIP-108: Language Coordination Layer1
Proposal: AIP-108 | Project: airflow | State: unknown
Everything can be set up in a Breeze shell. Go is installed automatically; pass --sdk java to install Java to "breeze shell" and "breeze start-airflow".
Tasks executed by the Java or Go SDK are wired up through three pi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:0"
] | 261 | en | 0.55 | 2026-09-21T12:13:28.728329Z |
aip-0108-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 1. Testing the Java SDK | Title: AIP-108: Language Coordination Layer1 — 1. Testing the Java SDK
Proposal: AIP-108 | Project: airflow | State: unknown
## 1. Testing the Java SDK
### Prerequisites
Requirement | Version |
---|---|
JDK | 11 |
Gradle | 8+ |
Airflow worker | HEAD |
### Create a new Gradle project
```bash
mkdir /files/aip108-... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:1"
] | 1,206 | en | 0.55 | 2026-09-21T12:13:28.728338Z |
aip-0108-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Create a new Go module | Title: AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Create a new Go module
Proposal: AIP-108 | Project: airflow | State: unknown
### Create a new Go module
```bash
mkdir /files/aip108-go-dag && cd /files/aip108-go-dag
go mod init example.com/aip108-go-dag
```
The Go SDK has no tagged release yet, ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:2"
] | 153 | en | 0.45 | 2026-09-21T12:13:28.728342Z |
aip-0108-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Write the tasks | Title: AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Write the tasks
Proposal: AIP-108 | Project: airflow | State: unknown
### Write the tasks
A Go bundle is a single package main. RegisterDags is the source of truth for the bundle's dag_id/task_ids, and AddTaskWithName pins each task to the task_id... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:3"
] | 404 | en | 0.55 | 2026-09-21T12:13:28.728346Z |
aip-0108-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Build the bundle | Title: AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Build the bundle
Proposal: AIP-108 | Project: airflow | State: unknown
### Build the bundle
airflow-go-pack builds the package, execs the binary to capture its manifest, and appends the source + manifest + AFBNDL01 trailer. The root command is the... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:4"
] | 204 | en | 0.55 | 2026-09-21T12:13:28.728349Z |
aip-0108-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Cross-platform builds (develop on macOS, deploy on Linux) | Title: AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Cross-platform builds (develop on macOS, deploy on Linux)
Proposal: AIP-108 | Project: airflow | State: unknown
### Cross-platform builds (develop on macOS, deploy on Linux)
The bundle is a native executable, so it must be built for the **worker's... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:5"
] | 154 | en | 0.425 | 2026-09-21T12:13:28.728353Z |
aip-0108-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=430408943 | Apache-2.0 | AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Integration test cases | Title: AIP-108: Language Coordination Layer1 — 2. Testing the Go SDK › Integration test cases
Proposal: AIP-108 | Project: airflow | State: unknown
### Integration test cases
Test Case ID | Test Objective | Test Steps | Prerequisite | Expected Outcome | Execution Status |
---|---|---|---|---|---|
GO-01 | (P0) Go tas... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:108",
"proposal_state:unknown",
"chunk:6"
] | 826 | en | 0.55 | 2026-09-21T12:13:28.728356Z |
aip-0109-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Motivation | Title: AIP-109: DAG Version Pinning — Motivation
Proposal: AIP-109 | Project: airflow | State: unknown
## Motivation
Airflow 3 introduces Dag Versioning (AIP-63: DAG Versioning), allowing the system to track the historical state of Dags. However, the scheduler continues to automatically use the *latest* parsed `DagVe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:0"
] | 1,096 | en | 0.475 | 2026-09-21T12:13:27.232839Z |
aip-0109-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › UI/UX Changes | Title: AIP-109: DAG Version Pinning — Proposed Changes › UI/UX Changes
Proposal: AIP-109 | Project: airflow | State: unknown
### UI/UX Changes
#### Dag View
Add an "Active Version" field on the Dag view UI right next to the "Latest Dag Version" field.
A pencil icon next to it can open a dropdown with all available ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:1"
] | 180 | en | 0.4 | 2026-09-21T12:13:27.232849Z |
aip-0109-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › Database Schema Changes | Title: AIP-109: DAG Version Pinning — Proposed Changes › Database Schema Changes
Proposal: AIP-109 | Project: airflow | State: unknown
### Database Schema Changes
#### Storing the Active Dag Version
Four constraints guide how the active version should be stored to ensure referential integrity, each with a desired ou... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:2"
] | 1,226 | en | 0.45 | 2026-09-21T12:13:27.232856Z |
aip-0109-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › Alternatives considered | Title: AIP-109: DAG Version Pinning — Proposed Changes › Alternatives considered
Proposal: AIP-109 | Project: airflow | State: unknown
### Alternatives considered
#### Pin the bundle itself (global bundle pin)
Keep a history of bundle versions the bundle has served and pin the whole bundle to one of them, so that ne... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:3"
] | 471 | en | 0.45 | 2026-09-21T12:13:27.232860Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.