evgenyslab opened a new issue, #28310:
URL: https://github.com/apache/airflow/issues/28310
### Apache Airflow version
2.5.0
### What happened
TriggerDagRunOperator will clear all run's in a time range around a
specified existing run_id when trying to re-trigger a single dag run.
Example:
```
trigger = TriggerDagRunOperator(
task_id="trigger_dag",
trigger_dag_id="{{ params.dag_id }}",
trigger_run_id= "{{ string_cast(run_id) }}",
reset_dag_run=True,
dag=dag,
wait_for_completion=False
)
```
The above will actually clear all run_id's that are within
`dag.clear(start_date=parsed_execution_date, end_date=parsed_execution_date)` -
this should be a run_id selector instead based on expected behaviour from
documentation.
### What you think should happen instead
The above will actually clear all run_id's that are within
`dag.clear(start_date=parsed_execution_date, end_date=parsed_execution_date)` -
this should be a run_id selector instead based on expected behaviour from
documentation.
### How to reproduce
_No response_
### Operating System
macOS 12.6.1
### Versions of Apache Airflow Providers
Apache/Airflow-2.2.2;
according to git this behaviour will exist in all version newer than 2.2.2
### Deployment
Docker-Compose
### Deployment details
_No response_
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
