Lee-W opened a new pull request, #69454:
URL: https://github.com/apache/airflow/pull/69454
### Why
`airflow partitions clear` silently reported no matching Dag runs when given
an inverted date window — a `--start-date` later than `--end-date`, or a
`--date 'a~b'` range where `a` is after `b`. The command treated it as a
valid-but-empty window instead of flagging the mistake, so a user who
transposed the two dates got a misleading "nothing matched" result rather than
an error. This is inconsistent with `dags clear
--partition-date-start/--partition-date-end` and the REST
`partition_date_start`/`partition_date_end` fields, which already reject
inverted
windows with the equivalent message.
### What
- Add an ordering check in `partition_command.clear`: when both bounds are
present and `start_date > end_date`, raise `SystemExit` with `--start-date must
be on or before --end-date.`
- Apply the check uniformly to both input forms — explicit `--start-date` /
`--end-date` flags and the `--date 'a~b'` range shorthand — by normalizing the
parsed range into the same `has_start` / `has_end` bounds before validating.
- Equal start and end dates remain valid (a single-day window).
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
