From commits-return-13446-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Mon Mar 26 16:42:29 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 E55DD180649 for ; Mon, 26 Mar 2018 16:42:28 +0200 (CEST) Received: (qmail 36184 invoked by uid 500); 26 Mar 2018 14:42:27 -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 36175 invoked by uid 99); 26 Mar 2018 14:42:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2018 14:42:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5B5801A04E6 for ; Mon, 26 Mar 2018 14:42:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.811 X-Spam-Level: X-Spam-Status: No, score=-101.811 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id EW9D9DxbKz6G for ; Mon, 26 Mar 2018 14:42:25 +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 D2B5B63468 for ; Mon, 26 Mar 2018 13:30:00 +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 62029E022F for ; Mon, 26 Mar 2018 13:30:00 +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 175B3214FA for ; Mon, 26 Mar 2018 13:30:00 +0000 (UTC) Date: Mon, 26 Mar 2018 13:30:00 +0000 (UTC) From: "sulphide (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-2250) execution_date logic seems broken in 1.9 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-2250?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] sulphide updated AIRFLOW-2250: ------------------------------ Description:=20 after upgrading to 1.9 some of our dags get execution_date's that are not a= ligned with our hardcoded start_date. this breaks our sensors, e.g. =C2=A0 [2018-03-23 20:06:21,781] \{base_task_runner.py:98} INFO - Subtask: [2018-0= 3-23 20:06:21,780] \{sensors.py:243} INFO - Poking for upstream_2017-12-06_= 2000.upstream_task=C2=A0on 2018-03-22T19:51:52.050448=C2=A0 =C2=A0 in this case our ExternalTaskSensor has a start_date with a start_time of 2= 100 and is pointing at the upstream dag and task with an execution_delta of= 1 hour.=20 the problem: the task_instance gets an execution_date of 2018-03-022T19:51:= 52.050448 but should be getting an execution_date of 2018-03-22T21:00:00 was: after upgrading to 1.9 some of our dags get execution_date's that are not a= ligned with our hardcoded start_date. this breaks our sensors, e.g. =C2=A0 [2018-03-23 20:06:21,781] \{base_task_runner.py:98} INFO - Subtask: [2018-0= 3-23 20:06:21,780] \{sensors.py:243} INFO - Poking for upstream_2017-12-06_= 2000.upstream_task=C2=A0on 2018-03-22T19:51:52.050448=C2=A0 =C2=A0 in this case our ExternalTaskSensor has a start_date with a start_time of 2= 100 and is pointing at the upstream dag and task with an execution_delta of= 1 hour.=20 *the problem* is that the task_instance gets an execution_date of 2018-03-0= 22T19:51:52.050448 but should be getting an execution_date of 2018-03-22T21= :00:00 > execution_date logic seems broken in 1.9 > ---------------------------------------- > > Key: AIRFLOW-2250 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2250 > Project: Apache Airflow > Issue Type: Bug > Reporter: sulphide > Priority: Major > Attachments: Screen Shot 2018-03-23 at 4.47.03 PM.png > > > after upgrading to 1.9 some of our dags get execution_date's that are not= aligned with our hardcoded start_date. this breaks our sensors, e.g. > =C2=A0 > [2018-03-23 20:06:21,781] \{base_task_runner.py:98} INFO - Subtask: [2018= -03-23 20:06:21,780] \{sensors.py:243} INFO - Poking for upstream_2017-12-0= 6_2000.upstream_task=C2=A0on 2018-03-22T19:51:52.050448=C2=A0 > =C2=A0 > in this case our ExternalTaskSensor has a start_date with a start_time of= 2100 and is pointing at the upstream dag and task with an execution_delta = of 1 hour.=20 > the problem: the task_instance gets an execution_date of 2018-03-022T19:5= 1:52.050448 but should be getting an execution_date of 2018-03-22T21:00:00 -- This message was sent by Atlassian JIRA (v7.6.3#76005)