we should hold off on this until @sashank makes forward progress with the date-time partitioning next week (tied to the scheduler). i think "Execution time" sounds like the time that the computation is occuring. I.e. if the computation were happening on oct-1 but processing the data from sept 15, I would guess that "Execution time" means oct 1, which is the opposite of this as I understand it.
I'm going to drop this—after discussing with @prha given the run config cleanup he's doing, I would prefer to rip all of this out entirely.
Instead of threading RunConfig through the config mapping context, we should have:
- A "pure" parent -> child config mapping API
- In @sashank 's work to create unit of work APIs, we should provide a way to wire Airflow's execution date up to config construction