[
https://issues.apache.org/jira/browse/AIRFLOW-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366124#comment-17366124
]
ASF GitHub Bot commented on AIRFLOW-1424:
-----------------------------------------
eladkal commented on pull request #2460:
URL: https://github.com/apache/airflow/pull/2460#issuecomment-864523808
> Let's target 2.2 with this. @ultrabug can you handle the merge conflicts?
mmm I think the reason behind this PR will no longer be valid after [AIP-39
Richer
scheduler_interval](https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-39+Richer+scheduler_interval).
The reason behind adding this column is that `execution_date` is confusing
thus exposing the `next_execution_date` in the UI will make things more clear
to the users. I think AIP-39 will solve the problem from the root because we
will have `schedule_date` that is seperated from
`execution_date`/`next_execution_date`
(`data_interval_start`/`data_interval_end`)
In any case I suggest at least to wait after AIP-39 is completed and then
revisit to see if this PR brings additional value.
--
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)
