[
https://issues.apache.org/jira/browse/AIRFLOW-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188037#comment-17188037
]
ASF GitHub Bot commented on AIRFLOW-1424:
-----------------------------------------
alexbegg commented on pull request #2460:
URL: https://github.com/apache/airflow/pull/2460#issuecomment-684083145
Another snag I ran into is I tried to replicate this functionality on top of
the latest master branch changes:
I can't figure out how to access the `schedulable_at` and `scheduled_in`
properties on the `DAG` model, because `dags.html` is only iterating on
`DagModel`s instead which is getting columns from the dag table of the db. I
know I can access the DAG object by importing the model and doing
`DAG(dag_id=dag.dag_id)` but I don't know how to do that in the template unless
I somehow make a method of the DagModel to get the dag object. Sorry, my flask
knowledge is a bit rusty.
I guess an alternative would be to make this asynchronous and not use the
property directly in the template.
----------------------------------------------------------------
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)
