Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8C3E7200AF8 for ; Thu, 5 May 2016 16:40:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8AD63160A03; Thu, 5 May 2016 14:40:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D2E4A1609F3 for ; Thu, 5 May 2016 16:40:16 +0200 (CEST) Received: (qmail 84313 invoked by uid 500); 5 May 2016 14:40:16 -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 84304 invoked by uid 99); 5 May 2016 14:40:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2016 14:40:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 946C6180148 for ; Thu, 5 May 2016 14:40:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id VE8M6TGxmnJ5 for ; Thu, 5 May 2016 14:40:14 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 20E535F365 for ; Thu, 5 May 2016 14:40:13 +0000 (UTC) Received: (qmail 83953 invoked by uid 99); 5 May 2016 14:40:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 May 2016 14:40:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E8B062C1F6A for ; Thu, 5 May 2016 14:40:12 +0000 (UTC) Date: Thu, 5 May 2016 14:40:12 +0000 (UTC) From: "Chris Riccomini (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-39) DagRun scheduled after end_date MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 05 May 2016 14:40:17 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272456#comment-15272456 ] Chris Riccomini commented on AIRFLOW-39: ---------------------------------------- +1 > DagRun scheduled after end_date > ------------------------------- > > Key: AIRFLOW-39 > URL: https://issues.apache.org/jira/browse/AIRFLOW-39 > Project: Apache Airflow > Issue Type: Wish > Affects Versions: Airflow 1.7.0 > Environment: - Airflow version: v1.7.0 > - Airflow components: webserver and scheduler with a postgres database and LocalExecutor > - Python Version: 2.7.9 > Reporter: dud > Assignee: Siddharth Anand > Priority: Minor > Attachments: 1_7_0_dag_runs_past_date_running.png, Head_master_dag_runs_past_date_failed.png, Jobs_view_only_shows_runs_within_start_end_range.png, Task_instance_view_only_shows_TIs_within_start_end_range.png, Tree_view_only_shows_runs_within_start_end_range.png, tutorial4.png, tutorial4_grpah.png > > > Hello > When I write a new DAG, it is automatically picked by the scheduler as intended. However the end_date parameter is not accounted when creating a DagRun, so that DagRuns scheduled after end_date are being displayed in the web interface and are staying in the running state forever as the scheduler doesn't launch them. > From my reading of the sources, the end_date paremeter is not used when creating a DagRun. > Is there any reason for this behaviour ? > Regards > dud -- This message was sent by Atlassian JIRA (v6.3.4#6332)