Airflow names child runs from TriggerDagRunOperator "triggered_from"
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 472
Description
### Description
Airflow names child runs from TriggerDagRunOperator as manual__..., even though no person manually started that backfill. It would be great if they can have a more detailed naming.
### Use case/motivation
_No response_
### Related issues
_No response_
### Are you willing to submit a 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)
Contributor guide
Research direction
Start at TriggerDagRunOperator and trace how it generates the child run ID, then inspect the related tests for run naming. Done means child runs triggered by this operator use a detailed name that identifies their trigger source rather than the manual__ prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100