Repository navigation
Conversation
An operator-initiated clear now deletes the task's state store rows, so a re-expanded dynamically mapped task never inherits the state of the item that previously occupied the same positional map_index. Automatic retries still share rows, so durable execution continues to resume a failed attempt from its last checkpoint.
potiuk
added
the
closed because of open PR limit
|
Hello @Kunal8954 - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 8 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Clearing a task instance now deletes its
task_state_storerows, so a re-expandeddynamically mapped task never inherits the state of the item that previously occupied
the same positional
map_index.The state store is keyed by positional
map_indexand previously survived anoperator-initiated clear. If the expanded upstream list changes between runs (an
insertion, deletion, or reordering), index N on the second attempt is a different
item than index N on the first, and would silently inherit the earlier item's state
(including a stored external-job reference), while the run still reports success.
Airflow's own clear path already regenerates the TaskInstance uuid and deletes XComs
in
clear_task_instances; this change adds the state store wipe in the same place.Automatic retries are not clears and still share rows, so durable execution continues
to resume a failed attempt from its last checkpoint. The docs (
resumable-tasks.rstand
task-state-store.rst) are updated to describe clearing as a controlled reset andto document the positional-index caveat for mapped tasks.
closes: #72725
Was generative AI tooling used to co-author this PR?
Generated-by: big-pickle (opencode/big-pickle) following the guidelines