[jira] [Commented] (AIRFLOW-2965) Add CLI command to find the next dag run.

["Siddharth Anand (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594394#comment-16594394 ] 

Siddharth Anand commented on AIRFLOW-2965:
------------------------------------------

This is a good ask! I recall it was requested a long time ago and somehow never made it to reality! Would you like to take a crack at it? You can send a note to the Dev list if someone would like to take it on as well!

-s

> Add CLI command to find the next dag run.
> -----------------------------------------
>
>                 Key: AIRFLOW-2965
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2965
>             Project: Apache Airflow
>          Issue Type: Task
>            Reporter: jack
>            Priority: Minor
>             Fix For: 1.10.1
>
>
> I have a dag with the following properties:
> {code:java}
> dag = DAG(
>     dag_id='mydag',
>     default_args=args,
>     schedule_interval='0 1 * * *',
>     max_active_runs=1,
>     catchup=False){code}
>  
>  
> This runs great.
> Last run is: 2018-08-26 01:00  (start date is 2018-08-27 01:00)
>  
> Now it's 2018-08-27 17:55 I decided to change my dag to:
>  
> {code:java}
> dag = DAG(
>     dag_id='mydag',
>     default_args=args,
>     schedule_interval='0 23 * * *',
>     max_active_runs=1,
>     catchup=False){code}
>  
> Now, I have no idea when will be the next dag run.
> Will it be today at 23:00? I can't be sure when the cycle is complete. I'm not even sure that this change will do what I wish.
> I'm sure you guys are expert and you can answer this question but most of us wouldn't know.
>  
> The scheduler has the knowledge when the dag is available for running. All I'm asking is to take that knowledge and create a CLI command that I will give the dag_id and it will tell me the next date/hour which my dag will be runnable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)