From commits-return-19243-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Mon Aug 27 17:01:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8AEC918067B for ; Mon, 27 Aug 2018 17:01:05 +0200 (CEST) Received: (qmail 93730 invoked by uid 500); 27 Aug 2018 15:01:03 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 93640 invoked by uid 99); 27 Aug 2018 15:01:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2018 15:01:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 03E42C5660 for ; Mon, 27 Aug 2018 15:01:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bV86FPQtLeGY for ; Mon, 27 Aug 2018 15:01:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 23C135F489 for ; Mon, 27 Aug 2018 15:01:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A218EE0A31 for ; Mon, 27 Aug 2018 15:01:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A6E6A26B62 for ; Mon, 27 Aug 2018 15:01:00 +0000 (UTC) Date: Mon, 27 Aug 2018 15:01:00 +0000 (UTC) From: "jack (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-2965) Add CLI command to find the next dag run. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRFLOW-2965?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] jack updated AIRFLOW-2965: -------------------------- Description:=20 I have a dag with the following properties: {code:java} dag =3D DAG( =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', =C2=A0=C2=A0=C2=A0 default_args=3Dargs, =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 1 * * *', =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} =C2=A0 =C2=A0 This runs great. Last run is: 2018-08-26 01:00=C2=A0 (start date is 2018-08-27 01:00) =C2=A0 Now it's 2018-08-27 17:55 I decided to change my dag to: =C2=A0 {code:java} dag =3D DAG( =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', =C2=A0=C2=A0=C2=A0 default_args=3Dargs, =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 23 * * *', =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} =C2=A0 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 u= s wouldn't know. =C2=A0 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 g= ive the dag_id and it will tell me the next date/hour which my dag will be = runnable. was: I have a dag with the following properties: {code:java} dag =3D DAG( =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', =C2=A0=C2=A0=C2=A0 default_args=3Dargs, =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 1 * * *', =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} =C2=A0 =C2=A0 This runs great. Last run is: 2018-08-26 01:00=C2=A0 (start date is 2018-08-27 01:00) =C2=A0 Now it's 2018-08-27 17:55 I decided to change my dag to: =C2=A0 {code:java} dag =3D DAG( =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', =C2=A0=C2=A0=C2=A0 default_args=3Dargs, =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 23 * * *', =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} =C2=A0 Now, I have no idea if the dag when will be the next run. Will it be today at 23:00? I can't be sure when the cycle is complete. I'm sure you guys are expert and you can answer this question but most of u= s wouldn't know. =C2=A0 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 g= ive the dag_id and it will tell me the next date/hour which my dag will be = runnable. > 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 =3D DAG( > =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', > =C2=A0=C2=A0=C2=A0 default_args=3Dargs, > =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 1 * * *', > =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, > =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} > =C2=A0 > =C2=A0 > This runs great. > Last run is: 2018-08-26 01:00=C2=A0 (start date is 2018-08-27 01:00) > =C2=A0 > Now it's 2018-08-27 17:55 I decided to change my dag to: > =C2=A0 > {code:java} > dag =3D DAG( > =C2=A0=C2=A0=C2=A0 dag_id=3D'mydag', > =C2=A0=C2=A0=C2=A0 default_args=3Dargs, > =C2=A0=C2=A0=C2=A0 schedule_interval=3D'0 23 * * *', > =C2=A0=C2=A0=C2=A0 max_active_runs=3D1, > =C2=A0=C2=A0=C2=A0 catchup=3DFalse){code} > =C2=A0 > 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. > =C2=A0 > The scheduler has the knowledge when the dag is available for running. Al= l 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 b= e runnable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)