ultrabug commented on pull request #2460: URL: https://github.com/apache/airflow/pull/2460#issuecomment-686728222
Hello @alexbegg 1. Yes indeed. The fact that all the scheduling logic is embedded in the `create_dag_run` which I read as "let's create a dag run" is forcing us to use the dry run trick to actually get the date. We could argue that another suitable manner to implement this would be to move the logic in a "what would be the next execution of this dag" function. But maybe dry run trick is enough. 2. intention is to get the next expected execution date 3. sounds sane not to indeed 4. as for column, I agree indeed As for your last comment, it's too long ago for me to get a proper answer. Did you find out something better since? ---------------------------------------------------------------- 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: [email protected]
