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-0109-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › API changes | Title: AIP-109: DAG Version Pinning — Proposed Changes › API changes
Proposal: AIP-109 | Project: airflow | State: unknown
### API changes
Extend the PATCH /dags APIs to manage Dags' active version.
#### Pin a Dag Version for newer runs
`PATCH /dags/{dag_id}?update_mask=active_dag_version_id`
`{"active_dag_version... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:4"
] | 433 | en | 0.6 | 2026-09-21T12:13:27.232864Z |
aip-0109-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › Scheduler Changes | Title: AIP-109: DAG Version Pinning — Proposed Changes › Scheduler Changes
Proposal: AIP-109 | Project: airflow | State: unknown
### Scheduler Changes
The scheduler's Dag run creation flow must be updated to respect the pinned version instead of defaulting to the latest bundle/version for *new* runs.
Applicability o... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:5"
] | 159 | en | 0.35 | 2026-09-21T12:13:27.232867Z |
aip-0109-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › Dag Processor Changes | Title: AIP-109: DAG Version Pinning — Proposed Changes › Dag Processor Changes
Proposal: AIP-109 | Project: airflow | State: unknown
### Dag Processor Changes
#### DagVersion Immutability (Pin Guard)
A pin is only meaningful if the version it references does not change underneath it. When the Dag Processor records a... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:6"
] | 760 | en | 0.45 | 2026-09-21T12:13:27.232871Z |
aip-0109-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Proposed Changes › Out of Scope | Title: AIP-109: DAG Version Pinning — Proposed Changes › Out of Scope
Proposal: AIP-109 | Project: airflow | State: unknown
### Out of Scope
To ensure this feature remains a focused execution primitive, the following are explicitly **out of scope. **The first two are capabilities Airflow will not provide, while the r... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:7"
] | 493 | en | 0.45 | 2026-09-21T12:13:27.232875Z |
aip-0109-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421958312 | Apache-2.0 | AIP-109: DAG Version Pinning — Edge cases and other considerations | Title: AIP-109: DAG Version Pinning — Edge cases and other considerations
Proposal: AIP-109 | Project: airflow | State: unknown
## Edge cases and other considerations
Listed below are some of the edge cases and considerations with this approach
#### Import Errors
Syntax errors or performance issues while parsing a ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:109",
"proposal_state:unknown",
"chunk:8"
] | 1,336 | en | 0.45 | 2026-09-21T12:13:27.232880Z |
aip-0111-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Motivation | Title: AIP-111: Task Loops — Motivation
Proposal: AIP-111 | Project: airflow | State: unknown
## Motivation
Airflow already runs your tasks deterministically and reliably. Loops let a runtime condition decide *how many times* to run a region of the DAG: the dynamism is focused on the loop count and the stop condition... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:0"
] | 463 | en | 0.45 | 2026-09-21T12:13:27.274971Z |
aip-0111-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Current workarounds and their limitations | Title: AIP-111: Task Loops — Current workarounds and their limitations
Proposal: AIP-111 | Project: airflow | State: unknown
## Current workarounds and their limitations
**Hard-code N copies of the region.**Works only to the hard-coded depth; changing it is a DAG edit and, under DAG versioning, a new DAG version. Thi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:2"
] | 153 | en | 0.375 | 2026-09-21T12:13:27.274982Z |
aip-0111-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Scope | Title: AIP-111: Task Loops — Scope
Proposal: AIP-111 | Project: airflow | State: unknown
## Scope
Deliver a **bounded, sequential, state-carrying loop over a Task Group**: it runs iterations in order (each building on the last), stops on a success criterion.
The number of iterations can be defined at runtime. Additi... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:3"
] | 174 | en | 0.35 | 2026-09-21T12:13:27.274985Z |
aip-0111-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Considerations | Title: AIP-111: Task Loops — Considerations
Proposal: AIP-111 | Project: airflow | State: unknown
## Considerations
**What change do you propose?**
Add .loop() to a Task Group. It turns the region into a **bounded, sequential loop**: it expands to max_iterations mapped instances, iteration i runs only after i-1 fini... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:4"
] | 1,486 | en | 0.575 | 2026-09-21T12:13:27.274988Z |
aip-0111-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Considerations | Title: AIP-111: Task Loops — Considerations
Proposal: AIP-111 | Project: airflow | State: unknown
Because a large cap that stops early leaves many skipped cells, and skipped elsewhere signals "branch not taken / upstream failed," the Grid needs a **distinct visual for "skipped because the loop finished normally"** so ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:5"
] | 649 | en | 0.45 | 2026-09-21T12:13:27.274992Z |
aip-0111-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Which users are affected? | Title: AIP-111: Task Loops — Which users are affected?
Proposal: AIP-111 | Project: airflow | State: unknown
## Which users are affected?
**DAG authors** gain an optional .loop() on tasks and Task Groups plus the loop accessor. No existing DAG is affected; the feature is opt-in.
**Platform teams.** A DAG that uses .... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:6"
] | 113 | en | 0.35 | 2026-09-21T12:13:27.274995Z |
aip-0111-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Migration Effort | Title: AIP-111: Task Loops — Migration Effort
Proposal: AIP-111 | Project: airflow | State: unknown
## Migration Effort
None for existing DAGs. Adopting loops is opt-in per region. The only platform consideration is the version floor above.
## Downsides
**Possible skip-tail materialization cost:**a run materializes... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:7"
] | 122 | en | 0.35 | 2026-09-21T12:13:27.274998Z |
aip-0111-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Out of scope | Title: AIP-111: Task Loops — Out of scope
Proposal: AIP-111 | Project: airflow | State: unknown
## Out of scope
**Mapping inside a loop**(parse-time rejected for this initial scope; the cheaper loop-under-fixed-mapping case is a candidate fast-follow).
## What defines this AIP as "done"?
- .loop(max_iterations=N, u... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:8"
] | 265 | en | 0.55 | 2026-09-21T12:13:27.275002Z |
aip-0111-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440303747 | Apache-2.0 | AIP-111: Task Loops — Open questions (for discussion) | Title: AIP-111: Task Loops — Open questions (for discussion)
Proposal: AIP-111 | Project: airflow | State: unknown
## Open questions (for discussion)
**Gate task id:**reserved (__loop_gate__, predictable, machinery-looking) vs. predicate-derived (refine.quality_reached, reads well but looks like user code and can col... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:111",
"proposal_state:unknown",
"chunk:9"
] | 132 | en | 0.35 | 2026-09-21T12:13:27.275005Z |
aip-0112-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Demo | Title: AIP-112: Task Steps — Demo
Proposal: AIP-112 | Project: airflow | State: unknown
## Demo
# Motivation
Airflow tasks today are atomic units of execution: a @task runs as one process, produces one log stream, retries as one unit. Real pipelines often want sub-structure inside a task, phases that you can observe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:0"
] | 687 | en | 0.55 | 2026-09-21T12:13:27.297482Z |
aip-0112-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — What change do you propose? | Title: AIP-112: Task Steps — What change do you propose?
Proposal: AIP-112 | Project: airflow | State: unknown
## What change do you propose?
Add a step() context manager to the Task SDK. It wraps a chunk of code inside a @task and gives it a name, a status, a duration, optional output chips, and live progress. Its s... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:1"
] | 1,168 | en | 0.625 | 2026-09-21T12:13:27.297489Z |
aip-0112-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Core abstraction | Title: AIP-112: Task Steps — Core abstraction
Proposal: AIP-112 | Project: airflow | State: unknown
## Core abstraction
The simplest use is wrapping a long-running loop to report progress, with no checkpointing and no new concepts:
```python
from airflow.sdk import step, task
@task
def sync_orders():
with step(... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:2"
] | 607 | en | 0.55 | 2026-09-21T12:13:27.297493Z |
aip-0112-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Mixed mode (default): observability and checkpoint reuse | Title: AIP-112: Task Steps — Mixed mode (default): observability and checkpoint reuse
Proposal: AIP-112 | Project: airflow | State: unknown
## Mixed mode (default): observability and checkpoint reuse
A @task is a Python function. step() blocks wrap chunks you want UI/log folds for; plain Python in between just runs. ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:3"
] | 213 | en | 0.475 | 2026-09-21T12:13:27.297496Z |
aip-0112-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Strict mode (opt-in): the precondition for retry_from_step | Title: AIP-112: Task Steps — Strict mode (opt-in): the precondition for retry_from_step
Proposal: AIP-112 | Project: airflow | State: unknown
## Strict mode (opt-in): the precondition for retry_from_step
```python
@task(strict_steps=True)
def my_pipeline():
with step("load_config") as s:
config = s.checkp... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:4"
] | 1,186 | en | 0.575 | 2026-09-21T12:13:27.297500Z |
aip-0112-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Where Steps render | Title: AIP-112: Task Steps — Where Steps render
Proposal: AIP-112 | Project: airflow | State: unknown
## Where Steps render
A "Steps" view inside the existing TI **Logs** tab. Users go to Logs to debug, so the structured view appears where logs already live. No new tab. Plus a **grid hover** progress hint, so a runni... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:5"
] | 247 | en | 0.45 | 2026-09-21T12:13:27.297504Z |
aip-0112-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Key UI decisions | Title: AIP-112: Task Steps — Key UI decisions
Proposal: AIP-112 | Project: airflow | State: unknown
## Key UI decisions
**Timeline strip is proportional to wall-clock.**A 35s untracked gap*looks*like 35s of the bar.**Gap thresholds.**Under 100ms invisible, 100ms to 5s a muted "untracked, 0.16s" connector, over 5s a f... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:6"
] | 164 | en | 0.375 | 2026-09-21T12:13:27.297507Z |
aip-0112-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304696 | Apache-2.0 | AIP-112: Task Steps — Backwards compatibility | Title: AIP-112: Task Steps — Backwards compatibility
Proposal: AIP-112 | Project: airflow | State: unknown
## Backwards compatibility
Tasks with no step() calls render exactly as today: no Steps view, no timeline, no new chrome. Opt-in is purely additive.
# Common Questions
**We already have log groups. Why do we n... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:112",
"proposal_state:unknown",
"chunk:7"
] | 553 | en | 0.475 | 2026-09-21T12:13:27.297510Z |
aip-0113-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups | Title: AIP-113: Dynamic Task Groups
Proposal: AIP-113 | Project: airflow | State: unknown
# Motivation
Dynamic task mapping (AIP-42) made **cardinality** dynamic: run the same task over a collection discovered at run time. What is still static is the **shape**, meaning which tasks run in a region and how they depend ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:0"
] | 305 | en | 0.55 | 2026-09-21T12:13:27.352961Z |
aip-0113-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Current workarounds and their limitations | Title: AIP-113: Dynamic Task Groups — Current workarounds and their limitations
Proposal: AIP-113 | Project: airflow | State: unknown
## Current workarounds and their limitations
**Branching.**A branch task already selects a subset: `choose_branch` returns a task id or a list of task ids, so any subset of its declare... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:1"
] | 971 | en | 0.5 | 2026-09-21T12:13:27.352968Z |
aip-0113-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — What change do you propose? | Title: AIP-113: Dynamic Task Groups — What change do you propose?
Proposal: AIP-113 | Project: airflow | State: unknown
## What change do you propose?
A Task Group whose members are chosen at run time from a declared catalog, authored as one construct and rendered as a group:
```python
DynamicTaskGroup(
group_id... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:2"
] | 319 | en | 0.525 | 2026-09-21T12:13:27.352972Z |
aip-0113-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — The catalog: allowlist and versioning anchor | Title: AIP-113: Dynamic Task Groups — The catalog: allowlist and versioning anchor
Proposal: AIP-113 | Project: airflow | State: unknown
## The catalog: allowlist and versioning anchor
The catalog is the list of tasks a planner may select and wire. A plan naming anything else is rejected before any task runs.
It is ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:3"
] | 236 | en | 0.45 | 2026-09-21T12:13:27.352975Z |
aip-0113-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — The plan | Title: AIP-113: Dynamic Task Groups — The plan
Proposal: AIP-113 | Project: airflow | State: unknown
## The plan
The plan is what one run's planner returns. It names the tasks that run, the edges between them, and the arguments each gets. A task is a record whose `id` identifies it within the plan and whose `entry` n... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:4"
] | 199 | en | 0.425 | 2026-09-21T12:13:27.352978Z |
aip-0113-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Guardrails | Title: AIP-113: Dynamic Task Groups — Guardrails
Proposal: AIP-113 | Project: airflow | State: unknown
## Guardrails
- `max_selected` is a required hard cap on how many entries one plan may select. Catalog size is the absolute bound.
- The catalog is a closed list, so a plan cannot name an undeclared task.
- Plan val... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:5"
] | 214 | en | 0.425 | 2026-09-21T12:13:27.352982Z |
aip-0113-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Runtime model | Title: AIP-113: Dynamic Task Groups — Runtime model
Proposal: AIP-113 | Project: airflow | State: unknown
## Runtime model
The group serializes as three nodes: the **generator**, the **region** that holds the emitted shape, and the terminal **merge**.
```java
<group>.plan ──▶ <group>.generated{ selected entries ─... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:6"
] | 470 | en | 0.575 | 2026-09-21T12:13:27.352985Z |
aip-0113-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — The merge node | Title: AIP-113: Dynamic Task Groups — The merge node
Proposal: AIP-113 | Project: airflow | State: unknown
## The merge node
The feature synthesizes the merge and fixes its success semantics instead of exposing a `trigger_rule`:
- It succeeds when the region terminates normally,
**including when the plan selects not... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:7"
] | 360 | en | 0.45 | 2026-09-21T12:13:27.352988Z |
aip-0113-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Where determinism still holds | Title: AIP-113: Dynamic Task Groups — Where determinism still holds
Proposal: AIP-113 | Project: airflow | State: unknown
## Where determinism still holds
Airflow does not become non-deterministic. The parent Dag's edges into and out of the group stay static and versioned, and what a run may vary is bounded by the ca... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:8"
] | 363 | en | 0.475 | 2026-09-21T12:13:27.352992Z |
aip-0113-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Interaction with Dag-level settings | Title: AIP-113: Dynamic Task Groups — Interaction with Dag-level settings
Proposal: AIP-113 | Project: airflow | State: unknown
## Interaction with Dag-level settings
A runtime-chosen shape runs into several settings that are fixed when the Dag is written.
**`dagrun_timeout`.**The author sets one budget without know... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:9"
] | 272 | en | 0.45 | 2026-09-21T12:13:27.352995Z |
aip-0113-10 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — The `plan` accessor | Title: AIP-113: Dynamic Task Groups — The `plan` accessor
Proposal: AIP-113 | Project: airflow | State: unknown
## The `plan` accessor
A catalog entry reads its wiring from the task context, so it never hard-codes task ids and can be reused across shapes:
- `plan.id` -- this instance's id in the plan, which is what ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:10"
] | 237 | en | 0.425 | 2026-09-21T12:13:27.352998Z |
aip-0113-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Examples | Title: AIP-113: Dynamic Task Groups — Examples
Proposal: AIP-113 | Project: airflow | State: unknown
## Examples
A deterministic planner, showing the parts that trip people up: how an entry reads its wiring instead of hard-coding task ids, where `inputs` come from, and downstream wiring with no `trigger_rule` on the ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:11"
] | 396 | en | 0.6 | 2026-09-21T12:13:27.353002Z |
aip-0113-12 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Rendering | Title: AIP-113: Dynamic Task Groups — Rendering
Proposal: AIP-113 | Project: airflow | State: unknown
## Rendering
The grid needs no new concept. Because only selected entries materialize, it lists the instances that ran under the region, labeled by entry.
The graph draws the emitted shape as an overlay: the static ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:12"
] | 193 | en | 0.35 | 2026-09-21T12:13:27.353005Z |
aip-0113-13 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Where the emitted plan lives, and for how long | Title: AIP-113: Dynamic Task Groups — Where the emitted plan lives, and for how long
Proposal: AIP-113 | Project: airflow | State: unknown
## Where the emitted plan lives, and for how long
The planner is user code, so it runs on a worker. The scheduler is what needs the result, because it does the sequencing. The pro... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:13"
] | 410 | en | 0.45 | 2026-09-21T12:13:27.353009Z |
aip-0113-14 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Composition with mapping and loops | Title: AIP-113: Dynamic Task Groups — Composition with mapping and loops
Proposal: AIP-113 | Project: airflow | State: unknown
## Composition with mapping and loops
Mapping, loops and dynamic groups all materialize a static region into runtime instances addressed by a single-dimension instance identity, which is why ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:14"
] | 412 | en | 0.425 | 2026-09-21T12:13:27.353012Z |
aip-0113-15 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304823 | Apache-2.0 | AIP-113: Dynamic Task Groups — Dag serialization and version skew | Title: AIP-113: Dynamic Task Groups — Dag serialization and version skew
Proposal: AIP-113 | Project: airflow | State: unknown
## Dag serialization and version skew
A dynamic group must fail closed for any reader that predates the feature. An older reader treating the region as an ordinary mapped group would run entr... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:113",
"proposal_state:unknown",
"chunk:15"
] | 1,353 | en | 0.575 | 2026-09-21T12:13:27.353017Z |
aip-0114-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440304131 | Apache-2.0 | AIP-114: Provider-supplied metrics backends via provider.yaml discovery — Considerations | Title: AIP-114: Provider-supplied metrics backends via provider.yaml discovery — Considerations
Proposal: AIP-114 | Project: airflow | State: unknown
## Considerations
### What change do you propose to make?
**New `metrics-backends` key in `provider.yaml`**so providers can declare their backend class(es) exactly how... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:114",
"proposal_state:unknown",
"chunk:1"
] | 1,058 | en | 0.55 | 2026-09-21T12:13:28.680838Z |
aip-0115-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Current Status | Title: AIP-115: On-Demand Task Sections — Current Status
Proposal: AIP-115 | Project: airflow | State: unknown
## Current Status
It was discussed in the Airflow Dev call that this AIP is better serviced as a plugin and a custom operator instead. https://github.com/apache/airflow/pull/69148 will now allow task instanc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:0"
] | 196 | en | 0.35 | 2026-09-21T12:13:27.451662Z |
aip-0115-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Demo | Title: AIP-115: On-Demand Task Sections — Demo
Proposal: AIP-115 | Project: airflow | State: unknown
## Demo
## Motivation
On-demand sections are uniquely useful only when all three of these hold at once:
- The optional work depends on artifacts/state that this specific run produced (so you can't cleanly move it to... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:1"
] | 260 | en | 0.475 | 2026-09-21T12:13:27.451667Z |
aip-0115-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Real World Examples | Title: AIP-115: On-Demand Task Sections — Real World Examples
Proposal: AIP-115 | Project: airflow | State: unknown
## Real World Examples
- Promote this build to production (CI/CD gate).
- Build → test → publish immutable artifact → deploy to staging → verify staging, all automatic. deploy_to_production + smoke test... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:2"
] | 342 | en | 0.475 | 2026-09-21T12:13:27.451671Z |
aip-0115-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Terminology | Title: AIP-115: On-Demand Task Sections — Terminology
Proposal: AIP-115 | Project: airflow | State: unknown
## Terminology
**On-demand section marker:**the "OnDemandSectionOperator" task that starts a optional subsection.**On-demand section:**the downstream tasks controlled by the marker.**Default skip:**the normal b... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:4"
] | 299 | en | 0.6 | 2026-09-21T12:13:27.451677Z |
aip-0115-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Why Not `trigger_rule="manual"`? | Title: AIP-115: On-Demand Task Sections — Why Not `trigger_rule="manual"`?
Proposal: AIP-115 | Project: airflow | State: unknown
## Why Not `trigger_rule="manual"`?
`trigger_rule` currently describes how upstream task states are evaluated. It answers questions such as "did all upstream tasks succeed?" or "did at leas... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:5"
] | 107 | en | 0.35 | 2026-09-21T12:13:27.451681Z |
aip-0115-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — UI/API Proposal | Title: AIP-115: On-Demand Task Sections — UI/API Proposal
Proposal: AIP-115 | Project: airflow | State: unknown
## UI/API Proposal
### UI
Graph view and the task-instance details view identify on-demand section markers by operator identity and, for a **successful, non-mapped** marker, expose a primary **"Run on-dema... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:7"
] | 149 | en | 0.45 | 2026-09-21T12:13:27.451687Z |
aip-0115-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=440305022 | Apache-2.0 | AIP-115: On-Demand Task Sections — Alternatives Considered | Title: AIP-115: On-Demand Task Sections — Alternatives Considered
Proposal: AIP-115 | Project: airflow | State: unknown
## Alternatives Considered
**Dag-run-scoped state store + `ShortCircuitOperator: `**A proposal to record a per-run key `(dag_id, run_id, key`) that a` ShortCircuitOperator `reads`(absent/False → ski... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:115",
"proposal_state:unknown",
"chunk:8"
] | 194 | en | 0.35 | 2026-09-21T12:13:27.451690Z |
aip-0116-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974654 | Apache-2.0 | AIP-116: Bounded Infrastructure Retries — Background and problem | Title: AIP-116: Bounded Infrastructure Retries — Background and problem
Proposal: AIP-116 | Project: airflow | State: draft
## Background and problem
An infrastructure interruption can stop healthy task code and consume an ordinary retry. A task with `retries=2` can fail after three such interruptions without complet... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:116",
"proposal_state:draft",
"chunk:0"
] | 113 | en | 0.35 | 2026-09-21T12:13:27.028367Z |
aip-0116-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974654 | Apache-2.0 | AIP-116: Bounded Infrastructure Retries — Proposal | Title: AIP-116: Bounded Infrastructure Retries — Proposal
Proposal: AIP-116 | Project: airflow | State: draft
## Proposal
### Administrator-controlled replacements
The administrator controls replacement attempts through one deployment-wide setting:
```java
[core]
max_infra_retries = 3
```
The setting defaults to `... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:116",
"proposal_state:draft",
"chunk:1"
] | 551 | en | 0.6 | 2026-09-21T12:13:27.028374Z |
aip-0116-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974654 | Apache-2.0 | AIP-116: Bounded Infrastructure Retries — Compatibility and scope | Title: AIP-116: Bounded Infrastructure Retries — Compatibility and scope
Proposal: AIP-116 | Project: airflow | State: draft
## Compatibility and scope
With the default of zero, deployments retain ordinary retry behavior while AIP-97 can still provide cause information. Enabling the policy can run a task more times t... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:116",
"proposal_state:draft",
"chunk:2"
] | 159 | en | 0.35 | 2026-09-21T12:13:27.028378Z |
aip-0116-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974654 | Apache-2.0 | AIP-116: Bounded Infrastructure Retries — Implementation and acceptance | Title: AIP-116: Bounded Infrastructure Retries — Implementation and acceptance
Proposal: AIP-116 | Project: airflow | State: draft
## Implementation and acceptance
The combined reference prototype is published at 6f5de9a with passing core CI. Its failure handler contains the deployment-only policy described here alon... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:116",
"proposal_state:draft",
"chunk:4"
] | 241 | en | 0.425 | 2026-09-21T12:13:27.028386Z |
aip-0117-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=446071748 | Apache-2.0 | AIP-117: Dynamic resolution of task fields — Motivation | Title: AIP-117: Dynamic resolution of task fields — Motivation
Proposal: AIP-117 | Project: airflow | State: unknown
## Motivation
A task's pool, pool_slots and priority_weight are fixed in the Dag source. There is no supported way to decide, when triggering a run, that specific tasks of that run should use a differe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:117",
"proposal_state:unknown",
"chunk:0"
] | 326 | en | 0.45 | 2026-09-21T12:13:27.510309Z |
aip-0117-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=446071748 | Apache-2.0 | AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make? | Title: AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make?
Proposal: AIP-117 | Project: airflow | State: unknown
### What change do you propose to make?
Two phases, both in scope for this AIP:
Trigger-time overrides. A new optional field on the run-creation request, with... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:117",
"proposal_state:unknown",
"chunk:1"
] | 1,508 | en | 0.5 | 2026-09-21T12:13:27.510315Z |
aip-0117-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=446071748 | Apache-2.0 | AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make? | Title: AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make?
Proposal: AIP-117 | Project: airflow | State: unknown
Guardrails. The administrator declares the envelope through a boolean column on slot_pool, default false, so only nominated pools are legal targets and default_... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:117",
"proposal_state:unknown",
"chunk:2"
] | 1,467 | en | 0.45 | 2026-09-21T12:13:27.510318Z |
aip-0117-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=446071748 | Apache-2.0 | AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make? | Title: AIP-117: Dynamic resolution of task fields — Considerations › What change do you propose to make?
Proposal: AIP-117 | Project: airflow | State: unknown
The phase 1 editor goes in the Advanced Options accordion of the trigger form (ConfigForm.tsx:98-124), with pool values from the existing usePoolServiceGetPools... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:117",
"proposal_state:unknown",
"chunk:3"
] | 495 | en | 0.35 | 2026-09-21T12:13:27.510322Z |
aip-0118-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — CI load and experimental performance | Title: AIP-118: Appendix — evidence and implementation details — CI load and experimental performance
Proposal: AIP-118 | Project: airflow | State: unknown
Supporting measurements and implementation notes for AIP-118 — CI on self-hosted runners. Configuration and source review are dated September 17, 2026; post-cleanu... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:0"
] | 307 | en | 0.425 | 2026-09-21T12:13:27.094228Z |
aip-0118-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Infrastructure and operating model | Title: AIP-118: Appendix — evidence and implementation details — Infrastructure and operating model
Proposal: AIP-118 | Project: airflow | State: unknown
## Infrastructure and operating model
### Airflow-operated EKS — architecture as built
GitHub queues jobs for an ARC runner scale set. Its listener connects outbou... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:1"
] | 788 | en | 0.45 | 2026-09-21T12:13:27.094234Z |
aip-0118-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Cost and shared budget | Title: AIP-118: Appendix — evidence and implementation details — Cost and shared budget
Proposal: AIP-118 | Project: airflow | State: unknown
## Cost and shared budget
### EKS per-run evidence
The experiments used different matrix sizes and capacity policies. Costs below are historical gross usage or estimates, befo... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:2"
] | 916 | en | 0.425 | 2026-09-21T12:13:27.094238Z |
aip-0118-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Required code adjustments | Title: AIP-118: Appendix — evidence and implementation details — Required code adjustments
Proposal: AIP-118 | Project: airflow | State: unknown
## Required code adjustments
The experiment has been simplified to remove obsolete CodeBuild workarounds. The following reflects Airflow revision `60f8d7ba53` and the EKS co... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:3"
] | 693 | en | 0.45 | 2026-09-21T12:13:27.094241Z |
aip-0118-04 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Routing Policy | Title: AIP-118: Appendix — evidence and implementation details — Routing Policy
Proposal: AIP-118 | Project: airflow | State: unknown
## Routing Policy
### Runners in Scope
Migrate scheduled Linux AMD and ARM canaries from the main branch of `apache/airflow` first. Committers may also explicitly route their own PRs ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:4"
] | 468 | en | 0.425 | 2026-09-21T12:13:27.094244Z |
aip-0118-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Validation results | Title: AIP-118: Appendix — evidence and implementation details — Validation results
Proposal: AIP-118 | Project: airflow | State: unknown
## Validation results
### EKS results
Public runs on `shahar1/airflow`, branch `test-eks-github-actions-runner`; historical conclusions checked against GitHub on **September 17, 2... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:5"
] | 516 | en | 0.45 | 2026-09-21T12:13:27.094248Z |
aip-0118-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974672 | Apache-2.0 | AIP-118: Appendix — evidence and implementation details — Evaluation and possible rollout | Title: AIP-118: Appendix — evidence and implementation details — Evaluation and possible rollout
Proposal: AIP-118 | Project: airflow | State: unknown
## Evaluation and possible rollout
RunsOn evaluation is underway alongside the existing CodeBuild and EKS evidence. Migrate scheduled canaries first, then make explici... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:118",
"proposal_state:unknown",
"chunk:6"
] | 359 | en | 0.425 | 2026-09-21T12:13:27.094251Z |
aip-0119-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account
Proposal: AIP-119 | Project: airflow | State: unknown
—
# 1. Motivation
The Apache Airflow project operates a dedicated AWS account. Today it hosts the
documentation site. In the near future it will also host self-hosted CI runners
on EK... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:0"
] | 656 | en | 0.425 | 2026-09-21T12:13:27.125743Z |
aip-0119-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 5.1 Cost Anomaly Detection monitor | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 5.1 Cost Anomaly Detection monitor
Proposal: AIP-119 | Project: airflow | State: unknown
## 5.1 Cost Anomaly Detection monitor
Create one monitor of type ***AWS services*** rather than account-level. Account-level
attribution is unnecess... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:1"
] | 233 | en | 0.425 | 2026-09-21T12:13:27.125752Z |
aip-0119-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 6.1 Operational note | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 6.1 Operational note
Proposal: AIP-119 | Project: airflow | State: unknown
## 6.1 Operational note
CloudFront publishes its default metrics to CloudWatch in ***us-east-1 only***,
irrespective of where the rest of the infrastructure resid... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:5"
] | 284 | en | 0.425 | 2026-09-21T12:13:27.125765Z |
aip-0119-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 6.4 Publish-correlated failures | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 6.4 Publish-correlated failures
Proposal: AIP-119 | Project: airflow | State: unknown
## 6.4 Publish-correlated failures
Documentation publishing is a batch event, so the highest-risk moment is known in
advance. A 4xx step change shortly... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:7"
] | 133 | en | 0.35 | 2026-09-21T12:13:27.125771Z |
aip-0119-08 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.1 Guardrails (autonomous — no human required) | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.1 Guardrails (autonomous — no human required)
Proposal: AIP-119 | Project: airflow | State: unknown
## 7.1 Guardrails (autonomous — no human required)
Listed in descending order of value.
***7.1.1 Do not run fork pull requests on self-... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:8"
] | 278 | en | 0.425 | 2026-09-21T12:13:27.125774Z |
aip-0119-09 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.2 Detection | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.2 Detection
Proposal: AIP-119 | Project: airflow | State: unknown
## 7.2 Detection
For what the guardrails cannot prevent.
Signal | Treatment | Rationale |
— | — | — |
Node count / EC2 instance-hours | * | CI load carries genuine wee... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:9"
] | 229 | en | 0.425 | 2026-09-21T12:13:27.125777Z |
aip-0119-11 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974695 | Apache-2.0 | AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.4 Why anomaly detection is the wrong primary tool for abuse | Title: AIP-119: Anomaly monitoring and guardrails for the Airflow AWS account — 7.4 Why anomaly detection is the wrong primary tool for abuse
Proposal: AIP-119 | Project: airflow | State: unknown
## 7.4 Why anomaly detection is the wrong primary tool for abuse
Worth stating explicitly, because it is counter-intuitive... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:119",
"proposal_state:unknown",
"chunk:11"
] | 700 | en | 0.425 | 2026-09-21T12:13:27.125784Z |
aip-0120-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 1. Motivation | Title: AIP-120: Run CI for external contributions in contributor forks — 1. Motivation
Proposal: AIP-120 | Project: airflow | State: draft
## 1. Motivation
Apache Airflow receives more pull requests than its maintainers can review. The volume has grown sharply with the widespread use of coding agents, and a substanti... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:0"
] | 308 | en | 0.425 | 2026-09-21T12:13:27.068593Z |
aip-0120-01 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 2. Proposal | Title: AIP-120: Run CI for external contributions in contributor forks — 2. Proposal
Proposal: AIP-120 | Project: airflow | State: draft
## 2. Proposal
**External contributions run their CI in the contributor's own fork. The project's CI runs for maintainers and for approved organisational stakeholders.**
### 2.1 Me... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:1"
] | 342 | en | 0.425 | 2026-09-21T12:13:27.068599Z |
aip-0120-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 3. Evidence | Title: AIP-120: Run CI for external contributions in contributor forks — 3. Evidence
Proposal: AIP-120 | Project: airflow | State: draft
## 3. Evidence
Measured 2026-06-20 to 2026-09-18 from the GitHub Search API (pull requests) and the Actions API (job timings). Caveats in §3.5.
### 3.1 Pull request volume and outc... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:2"
] | 792 | en | 0.425 | 2026-09-21T12:13:27.068602Z |
aip-0120-03 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 4. Why this shape | Title: AIP-120: Run CI for external contributions in contributor forks — 4. Why this shape
Proposal: AIP-120 | Project: airflow | State: draft
## 4. Why this shape
### 4.1 It is simple
Many approaches to pull request volume have been discussed over time, and most were structurally complex: new triage tiers, new labe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:3"
] | 312 | en | 0.425 | 2026-09-21T12:13:27.068605Z |
aip-0120-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 6. Objections | Title: AIP-120: Run CI for external contributions in contributor forks — 6. Objections
Proposal: AIP-120 | Project: airflow | State: draft
## 6. Objections
### 6.1 "This makes Airflow pay-to-contribute"
**The objection.** Gating CI behind Actions minutes means contributors exceeding the free tier must pay to partici... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:5"
] | 472 | en | 0.425 | 2026-09-21T12:13:27.068612Z |
aip-0120-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 7. Alternatives considered | Title: AIP-120: Run CI for external contributions in contributor forks — 7. Alternatives considered
Proposal: AIP-120 | Project: airflow | State: draft
## 7. Alternatives considered
**Do nothing.** Volume grows; review capacity does not. Rejected.
**Issue-gating (§6.3).** Complementary rather than alternative.
**Pe... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:6"
] | 279 | en | 0.425 | 2026-09-21T12:13:27.068615Z |
aip-0120-07 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974711 | Apache-2.0 | AIP-120: Run CI for external contributions in contributor forks — 9. Rollout | Title: AIP-120: Run CI for external contributions in contributor forks — 9. Rollout
Proposal: AIP-120 | Project: airflow | State: draft
## 9. Rollout
Stage | Deliverable |
---|---|
1 | done, §3. Optionally extend to a full CI census (§8.6) |
2 | `[DISCUSS]` on dev@ — a community policy change needing broad input, n... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:120",
"proposal_state:draft",
"chunk:7"
] | 749 | en | 0.45 | 2026-09-21T12:13:27.068618Z |
aip-0121-00 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974742 | Apache-2.0 | AIP-121: Introduce a PollingTrigger Lifecycle Framework — Motivation | Title: AIP-121: Introduce a PollingTrigger Lifecycle Framework — Motivation
Proposal: AIP-121 | Project: airflow | State: unknown
## Motivation
Deferrable operators move long-running waits from workers to the Triggerer, but `BaseTrigger` intentionally provides only a minimal contract: serialization and an asynchronou... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:121",
"proposal_state:unknown",
"chunk:0"
] | 337 | en | 0.425 | 2026-09-21T12:13:27.045585Z |
aip-0121-02 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974742 | Apache-2.0 | AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › What change do you propose to make? | Title: AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › What change do you propose to make?
Proposal: AIP-121 | Project: airflow | State: unknown
### What change do you propose to make?
Add an optional core `PollingTrigger` base class that inherits from `BaseTrigger` and owns the generic lif... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:121",
"proposal_state:unknown",
"chunk:2"
] | 955 | en | 0.55 | 2026-09-21T12:13:27.045595Z |
aip-0121-05 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974742 | Apache-2.0 | AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › How are users affected by the change? (e.g. DB upgrade required?) | Title: AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › How are users affected by the change? (e.g. DB upgrade required?)
Proposal: AIP-121 | Project: airflow | State: unknown
### How are users affected by the change? (e.g. DB upgrade required?)
There is no database migration, configuration ... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:121",
"proposal_state:unknown",
"chunk:5"
] | 185 | en | 0.35 | 2026-09-21T12:13:27.045604Z |
aip-0121-06 | docs | https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=451974742 | Apache-2.0 | AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › Other considerations? | Title: AIP-121: Introduce a PollingTrigger Lifecycle Framework — Considerations › Other considerations?
Proposal: AIP-121 | Project: airflow | State: unknown
### Other considerations?
The implementation and its tests must establish the following guardrails:
Polling hooks must be asynchronous and must not block the T... | airflow | [
"design_proposal",
"proposal_type:AIP",
"proposal_number:121",
"proposal_state:unknown",
"chunk:6"
] | 486 | en | 0.425 | 2026-09-21T12:13:27.045607Z |
arxiv-1802.10233-00 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources
arXiv: 1802.10233 | License: CC-BY-4.0
Abstract: Apache Calcite is a foundational software framework that provides query processing, optimization, and query language support to many popular open-source data p... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:0"
] | 1,203 | en | 0.575 | 2026-09-21T09:49:10.341633Z |
arxiv-1802.10233-01 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 2. Related Work | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 2. Related Work
arXiv: 1802.10233
## 2. Related Work
Though Calcite is currently the most widely adopted optimizer for big-data analytics in the Hadoop ecosystem, many of the ideas that lie behind it are n... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:1"
] | 607 | en | 0.525 | 2026-09-21T09:49:10.341645Z |
arxiv-1802.10233-02 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 3. Architecture | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 3. Architecture
arXiv: 1802.10233
## 3. Architecture
Calcite contains many of the pieces that comprise a typical database management system. However, it omits some key components, e.g., storage of data, al... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:2"
] | 481 | en | 0.425 | 2026-09-21T09:49:10.341649Z |
arxiv-1802.10233-03 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 4. Query Algebra | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 4. Query Algebra
arXiv: 1802.10233
## 4. Query Algebra
Operators. Relational algebra (Codd, 1970) lies at the core of Calcite. In addition to the operators that express the most common data manipulation op... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:3"
] | 551 | en | 0.45 | 2026-09-21T09:49:10.341653Z |
arxiv-1802.10233-04 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 5. Adapters | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 5. Adapters
arXiv: 1802.10233
## 5. Adapters
An adapter is an architectural pattern that defines how Calcite incorporates diverse data sources for general access. Figure 3 depicts its components. Essential... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:4"
] | 554 | en | 0.4 | 2026-09-21T09:49:10.341656Z |
arxiv-1802.10233-05 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 6. Query Processing and Optimization | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 6. Query Processing and Optimization
arXiv: 1802.10233
## 6. Query Processing and Optimization
The query optimizer is the main component in the framework. Calcite optimizes queries by repeatedly applying p... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:5"
] | 1,477 | en | 0.525 | 2026-09-21T09:49:10.341660Z |
arxiv-1802.10233-06 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 7. Extending Calcite | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 7. Extending Calcite
arXiv: 1802.10233
## 7. Extending Calcite
As we have mentioned in the previous sections, Calcite is not only tailored towards SQL processing. In fact, Calcite provides extensions to SQ... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:6"
] | 764 | en | 0.45 | 2026-09-21T09:49:10.341663Z |
arxiv-1802.10233-07 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 8. Industry and academia adoption | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 8. Industry and academia adoption
arXiv: 1802.10233
## 8. Industry and academia adoption
Calcite enjoys wide adoption, specially among open-source projects used in industry. As Calcite provides certain int... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:7"
] | 1,131 | en | 0.575 | 2026-09-21T09:49:10.341667Z |
arxiv-1802.10233-08 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 9. Future Work | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 9. Future Work
arXiv: 1802.10233
## 9. Future Work
The future work on Calcite will focus on the development of the new features, and the expansion of its adapter architecture:
- •
Enhancements to the desi... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:8"
] | 472 | en | 0.45 | 2026-09-21T09:49:10.341670Z |
arxiv-1802.10233-09 | arxiv | https://arxiv.org/abs/1802.10233 | CC-BY-4.0 | Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 10. Conclusion | Title: Apache Calcite: A Foundational Framework for Optimized Query Processing Over Heterogeneous Data Sources — 10. Conclusion
arXiv: 1802.10233
## 10. Conclusion
Emerging data management practices and associated analytic uses of data continue to evolve towards an increasingly diverse, and heterogeneous spectrum of ... | papers | [
"paper",
"arxiv_id:1802.10233",
"relevance:4",
"chunk:9"
] | 239 | en | 0.45 | 2026-09-21T09:49:10.341673Z |
arxiv-1907.12817-00 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters
arXiv: 1907.12817 | License: CC-BY-4.0
Abstract: Process Mining is a branch of Data Science that aims to extract process-related information from event data contained in information systems, that is steadily increasing i... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:0"
] | 1,256 | en | 0.525 | 2026-09-21T09:48:30.698002Z |
arxiv-1907.12817-01 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 2 Related Work | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 2 Related Work
arXiv: 1907.12817
## 2 Related Work
The XES standard:
several formats have been proposed during the years for the standard storage of event logs in process mining. The IEEE standard is XES [19], for whi... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:1"
] | 306 | en | 0.475 | 2026-09-21T09:48:30.698014Z |
arxiv-1907.12817-02 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 3 Background | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 3 Background
arXiv: 1907.12817
## 3 Background
### 3.1 Event Logs: Definition and Considerations
In this section, the notion of event log, i.e., a collection of events recorded in the execution of a business process ... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:2"
] | 979 | en | 0.5 | 2026-09-21T09:48:30.698018Z |
arxiv-1907.12817-03 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 4 Approach: Complexity of operations on Attribute Maps | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 4 Approach: Complexity of operations on Attribute Maps
arXiv: 1907.12817
## 4 Approach: Complexity of operations on Attribute Maps
The aim of this section is to present the complexity of retrieval and of the Directly-... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:3"
] | 324 | en | 0.425 | 2026-09-21T09:48:30.698022Z |
arxiv-1907.12817-04 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes
arXiv: 1907.12817
## 5 Approach: Dataframes
This section introduces the techniques that are necessary to do process mining on top of a different structure, i.e. the dataframe. Dataframes can ing... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:4"
] | 142 | en | 0.35 | 2026-09-21T09:48:30.698025Z |
arxiv-1907.12817-05 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.1 Definition of Dataframes | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.1 Definition of Dataframes
arXiv: 1907.12817
### 5.1 Definition of Dataframes
To introduce the concept of dataframe, one could think to a set of attribute names (columns) associated to the v... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:5"
] | 257 | en | 0.425 | 2026-09-21T09:48:30.698028Z |
arxiv-1907.12817-06 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.2 Simple Implementation of a Dataframe, Conversion from Event Logs to Dataframes | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.2 Simple Implementation of a Dataframe, Conversion from Event Logs to Dataframes
arXiv: 1907.12817
### 5.2 Simple Implementation of a Dataframe, Conversion from Event Logs to Dataframes
The ... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:6"
] | 268 | en | 0.475 | 2026-09-21T09:48:30.698031Z |
arxiv-1907.12817-07 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.3 Transformation functions | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.3 Transformation functions
arXiv: 1907.12817
### 5.3 Transformation functions
We introduce the following functions in order to be able to perform process mining operations on top of a datafr... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:7"
] | 325 | en | 0.425 | 2026-09-21T09:48:30.698035Z |
arxiv-1907.12817-08 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.4 Possibility to calculate the Directly-Follows Graph on top of dataframes | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.4 Possibility to calculate the Directly-Follows Graph on top of dataframes
arXiv: 1907.12817
### 5.4 Possibility to calculate the Directly-Follows Graph on top of dataframes
In this section,... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:8"
] | 351 | en | 0.425 | 2026-09-21T09:48:30.698038Z |
arxiv-1907.12817-09 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.5 Complexity Estimation on Logs and Dataframe Implementations | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 5 Approach: Dataframes › 5.5 Complexity Estimation on Logs and Dataframe Implementations
arXiv: 1907.12817
### 5.5 Complexity Estimation on Logs and Dataframe Implementations
Filtering: Filtering on the attribute valu... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:9"
] | 557 | en | 0.475 | 2026-09-21T09:48:30.698041Z |
arxiv-1907.12817-10 | arxiv | https://arxiv.org/abs/1907.12817 | CC-BY-4.0 | Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 6 Assessment | Title: Increasing Scalability of Process Mining using Event Dataframes: How Data Structure Matters — 6 Assessment
arXiv: 1907.12817
## 6 Assessment
In this section, an assessment of the speed of a dataframe implementation (Pandas), that can ingest data from the Parquet columnar format is done on some popular event lo... | papers | [
"paper",
"arxiv_id:1907.12817",
"relevance:4",
"chunk:10"
] | 483 | en | 0.475 | 2026-09-21T09:48:30.698044Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.