GitHub user potiuk added a comment to the discussion: Add the ability to backfill a DAG based on past Asset Events
Probably what you want: * your asset should have some "extra" which will tell (say for daily dag) "Wed 31, Dec 2025" - this will "link" DagRun triggered by the asset with the date * then you want to have an ability of triggering past Dag runs with (say) alll past days of december - this means that you need to create 30 asset events - each of them should have extra reflecting the day you want to associate with such dag run * then (you should want to have two variants of your dag (using Dynamic Dag generation) - one with downstream triggering and one without it (if you want those past dag runs to trigger downstream dags - use variant 1, if not - use variant 2) This all is easiest done with a script - because you need some things that your dag will handle by convention: * associating date with your asset triggered dag (by custom extra) * handling no downstream This is - if I understand correctly - because for some strange reason you do not want to use timetables and scheduling and data intervals (which is more appropriate for such "timed" dag runs - why you want to do it is a mistery, bycause it seems like custom emulating of the "data interval" feature that "scheduled" dags have, but that looks all like some strange custom approach that you want to use without understanding that scheduled dags are best run by ... schedule - not assets. That seems like using screwdriver to put the nail in, and if you want to do it on your own - feel free, but the feature of scheduled dags is in airlfow long before assets, and emulating it with assets, when it is fully featured, scheduled based implementation makes completely no sense for me. GitHub link: https://github.com/apache/airflow/discussions/59886#discussioncomment-15381296 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
