GitHub user hnomichith added a comment to the discussion: Add the ability to backfill a DAG based on past Asset Events
I understand better now about why "backfill" is not the feature I would need in my usecase. Thank you for the explanation. > Logically what you are asking for is ability to "clear" certain, selected dag > runs. Not exactly. If you take the scenario I described above, when I want to "catch-up" DAG_2, it does not have any DAG runs yet. There's nothing I can select and clear. Therefore, the two options you are mentioning does not answer my need. I could select and clear `DAG_1` (it's the first of the two currently available work-around I mentioned in my initial message), but it will imply re-running some tasks that are not helpful, and could even be harmful. Coming back to what I initially suggested: - the POST `/api/v2/dags/:dag_id/assets/queuedEvents` endpoint would allow to flexibly create only the necessary DAG runs. - the name filter on the GET `/api/v2/assets/events` would allow me to precisely search for the events I need to queue The third step of my initial suggestion was about enriching the "backfill" feature in the UI, but I understand from your explanations it would be a mix of concerns, so not something to consider. Contributing is a considered option, whether from me or my team members, but I'd rather agreeing on the need and the solution before :) GitHub link: https://github.com/apache/airflow/discussions/59886#discussioncomment-15380286 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
