feat(cli): add `partitions clear` to reset DagRun partition fields by Lee-W · Pull Request #66520 · apache/airflow

Lee-W · 2026-05-07T08:47:10Z

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

Lee-W · 2026-05-07T08:47:10Z

part of #65921

Why

airflow tasks clear --start-date / --end-date filters by logical_date, so it cannot reach Dag runs whose partition_date / partition_key is what identifies them (rollup or offset partitions). Today the only ways to bulk-reprocess such runs are N API calls or N UI clicks.

What

Add airflow dags clear <dag_id> with three mutually-exclusive selectors:
- --run-id (single run)
- --partition-key (every run with that exact key)
- --partition-date-start / --partition-date-end (inclusive partition_date window; runs with NULL partition_date are never matched;
  inverted window is rejected)
Reuse Dag.clear() per matched run_id, so TI reset + Dag run re-queue behave identically to every other clear path.
Print a listing (run_id, partition_key, partition_date) before prompting; --yes skips the prompt.

Was generative AI tooling used to co-author this PR?

Yes (please specify the tool below)

Generated-by: [Claude] following the guidelines

Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

potiuk · 2026-05-09T20:27:13Z

Rebase is needed I guess.

jason810496

LGTM overall. Not sure do I understand the batch clearing logic correctly.

jason810496

LGTM overall, please feel free to address in follow-up, non-blocking.

Introduce a new `airflow partitions` command group with a `clear` action that nulls out `partition_key` and `partition_date` on one or more DagRuns. Useful when migrating off a partitioned timetable or fixing a Dag run whose partition metadata was set incorrectly. Targeting: - `--dag-id` (required) - `--run-id` for a single run, or - `--start-date` / `--end-date` to clear a `partition_date` range (the two modes are mutually exclusive) Safety: - `--dry-run` previews matching runs without writing - Prints the existing `partition_key` / `partition_date` before clearing each run, and skips runs already cleared

Augment `airflow partitions clear` with `--clear-task-instances`: in addition to nulling `partition_key` / `partition_date`, clear the matched DagRuns' task instances so finished runs go back to QUEUED and re-execute. Useful after fixing partition metadata when the runs themselves should also re-run against the corrected logic. Behavior: - Default behavior is unchanged — only partition fields are nulled. - With `--clear-task-instances`, runs whose partition fields are already None are no longer skipped (their TIs are still cleared). - `--dry-run` reports both projected actions without writing.

- `--partition-key VALUE`: clear all DagRuns whose partition_key matches this exact value. - `--date a~b`: shorthand range syntax equivalent to `--start-date a --end-date b`. The four selection modes (--run-id, --partition-key, --start-date/--end-date, --date) are mutually exclusive.

…s clear

boring-cyborgBot added the area:CLI label May 7, 2026

Lee-W force-pushed the partitions-clear branch 5 times, most recently from f4a47d7 to af063eaCompare May 8, 2026 13:06

Lee-W marked this pull request as ready for review May 8, 2026 13:07

Lee-W requested review from bugraoz93, dheerajturaga and potiuk as code owners May 8, 2026 13:07

Lee-W force-pushed the partitions-clear branch 2 times, most recently from b809562 to e842cfaCompare May 11, 2026 04:27

Lee-W requested a review from uranusjr May 11, 2026 06:27

Lee-W added this to AIP-76 Asset Partitioning May 11, 2026

Lee-W moved this to In Review in AIP-76 Asset Partitioning May 11, 2026

Lee-W force-pushed the partitions-clear branch 3 times, most recently from 3481fdb to dc42fcaCompare May 19, 2026 10:25

uranusjr reviewed May 20, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated

uranusjr reviewed May 20, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated

uranusjr reviewed May 20, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated

uranusjr reviewed May 20, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/cli_config.py

Lee-W force-pushed the partitions-clear branch 3 times, most recently from 961c171 to 1f1e52aCompare May 21, 2026 14:21

Lee-W requested a review from uranusjr May 21, 2026 15:23

Lee-W force-pushed the partitions-clear branch from 1f1e52a to 53a4e02Compare May 22, 2026 00:12

jason810496 reviewed May 25, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated
Comment threadairflow-core/src/airflow/cli/commands/partition_command.py

Lee-W force-pushed the partitions-clear branch from 53a4e02 to ed18131Compare May 25, 2026 12:54

Lee-W force-pushed the partitions-clear branch from ed18131 to c501951Compare May 25, 2026 14:20

Lee-W requested a review from jason810496 May 25, 2026 15:27

Lee-W force-pushed the partitions-clear branch from c501951 to 20b1d9dCompare May 25, 2026 15:28

jason810496 approved these changes May 26, 2026
View reviewed changes

Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated
Comment threadairflow-core/src/airflow/cli/commands/partition_command.py Outdated
Comment threadairflow-core/src/airflow/cli/commands/partition_command.py

Lee-W force-pushed the partitions-clear branch 2 times, most recently from a9e83e6 to 995da42Compare May 27, 2026 01:40

Lee-W added 9 commits May 27, 2026 17:49

fixup! feat(cli): add --partition-key and --date filters to partition…
cbfaa35
…s clear

fixup! feat(cli): add --clear-task-instances flag to partitions clear
1b3dc5a

fixup! feat(cli): add --partition-key and --date filters to partition…
1ed6b05
…s clear

fixup! feat(cli): add --clear-task-instances flag to partitions clear
bc924a1

fixup! feat(cli): add --partition-key and --date filters to partition…
256d631
…s clear

fixup! feat(cli): add --partition-key and --date filters to partition…
3d73d11
…s clear

Lee-W force-pushed the partitions-clear branch from 995da42 to 3d73d11Compare May 27, 2026 09:49

Lee-W merged commit 07859aa into apache:mainMay 27, 2026
143 checks passed

Lee-W deleted the partitions-clear branch May 27, 2026 11:54

github-project-automationBot moved this from In Review to Done in AIP-76 Asset Partitioning May 27, 2026

kaxil mentioned this pull request May 28, 2026
AIP-76: Hold Dag run until all upstream partitions arrive #64571
Merged
1 task

vatsrahul1001 added this to the Airflow 3.3.0 milestone Jun 15, 2026