Repository navigation
Idempotency: downstream rollup behavior when an upstream partition is cleared and re-run #65923
Description
Body
What
When a downstream rollup has already fired for a window that included an upstream partition, and that upstream partition is later cleared and re-run, the framework needs a defined behavior. Example: the monthly rollup for 2026-03 already fired with 2026-03-15 included; user clears and re-runs 2026-03-15. Does the rollup reprocess, hold, or no-op?
Open question
Auto re-trigger the rollup, require explicit user action, or expose a per-timetable policy?
Related
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Activity