[
https://issues.apache.org/jira/browse/AIRFLOW-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185042#comment-17185042
]
ASF GitHub Bot commented on AIRFLOW-1424:
-----------------------------------------
ultrabug commented on pull request #2460:
URL: https://github.com/apache/airflow/pull/2460#issuecomment-680753848
@ryw thanks.
Taking into account the last comment from @JeffryMAC in #10556 and what
@eladkal is pointing out on #5787 I think that I should wait until you guys
settle on what you want first if that's okay with you @ryw?
Else I have the feeling that this PR will again stand in the middle of a
debate so I'd rather have it settled first ;)
----------------------------------------------------------------
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]
> Make the next execution date of DAGs visible
> --------------------------------------------
>
> Key: AIRFLOW-1424
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1424
> Project: Apache Airflow
> Issue Type: New Feature
> Components: DAG
> Reporter: Ultrabug
> Priority: Major
>
> The scheduler's DAG run creation logic can be tricky and one is
> easily confused with the start_date + interval
> and period end scheduling way of thinking.
> It would ease airflow's usage to add a next execution field to DAGs
> so that we can very easily see the (un)famous period end after which
> the scheduler will create a new DAG run for our workflows.
> These patches are a simple way to implement this on the DAG model
> and make use of this in the interface.
> Screenshots are on the github PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
