You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/09/04 17:24:03 UTC

[GitHub] [airflow] dstandish edited a comment on issue #5787: [AIRFLOW-5172] Add choice of interval edge scheduling

dstandish edited a comment on issue #5787: [AIRFLOW-5172] Add choice of interval edge scheduling
URL: https://github.com/apache/airflow/pull/5787#issuecomment-528000809
 
 
   @iroddis instead why not just add a `run_date` property to DagRun, and make it available in template context?
   It seems to me this would provide the clarity you seek without having to add additional configuration or changes to scheduler.   
   Adding run date would make explicit the run date vs execution date distinction.  
   Adding run date would allow execution_date to be consistently defined (as opposed to sometimes meaning run date and other times meaning last-run-date).
   And in the same dag, while one task might want use "execution_date", for another task "run_date" might be more appropriate.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services