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 25776200C29 for ; Tue, 28 Feb 2017 23:25:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 23A94160B7C; Tue, 28 Feb 2017 22:25:49 +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 6EF81160B59 for ; Tue, 28 Feb 2017 23:25:48 +0100 (CET) Received: (qmail 12169 invoked by uid 500); 28 Feb 2017 22:25:47 -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 12160 invoked by uid 99); 28 Feb 2017 22:25:47 -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; Tue, 28 Feb 2017 22:25:47 +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 235F1C6AA2 for ; Tue, 28 Feb 2017 22:25:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] 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 TlFNQ2XYeeKD for ; Tue, 28 Feb 2017 22:25:46 +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 43DC05F23A for ; Tue, 28 Feb 2017 22:25:46 +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 B690CE02AB for ; Tue, 28 Feb 2017 22:25:45 +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 7354F24154 for ; Tue, 28 Feb 2017 22:25:45 +0000 (UTC) Date: Tue, 28 Feb 2017 22:25:45 +0000 (UTC) From: "Bolke de Bruin (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-920) Can't mark non-existent tasks as successful from graph view MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Feb 2017 22:25:49 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888974#comment-15888974 ] Bolke de Bruin commented on AIRFLOW-920: ---------------------------------------- [~aoen] It does propagate in its current form: if you mark success a "subdag" operator from its parent dag it will mark success all tasks part of that subdag. My PR just verifies the tree of the dag to make sure dag runs are created for any missing subdag dag runs. I consider this to be something of a hack as it is in my opinion the wrong place to do it (the webserver). > Can't mark non-existent tasks as successful from graph view > ----------------------------------------------------------- > > Key: AIRFLOW-920 > URL: https://issues.apache.org/jira/browse/AIRFLOW-920 > Project: Apache Airflow > Issue Type: Sub-task > Affects Versions: 1.8.0rc4 > Reporter: Dan Davydov > Assignee: Bolke de Bruin > > If you want to add a subdag operator with depends on past set to an existing dag you need to mark the subdag as successful in the UI in order for it to start running. Previously this was possible by mark-successing the non-existent task instance/dagrun in the UI via the graph view. Now when you try to mark the task successful Airflow gives an empty list of tasks that it is going to try to mark successful, probably because the task instance/dagrun do not exist. > Repro steps: > - Create a DAG with a dummy task > - Let this DAG run for one dagrun > - Add a new subdag operator that contains a dummy operator to this DAG that > has depends_on_past set to true > - click on the white square for the new subdag operator in the DAGs first > dagrun > - Click "Zoom into subdag" (takes you to the graph view for the subdag) > - Click the dummy task in the graph view and click "Mark Success" > - Observe that the list of tasks to mark as success is empty (it should > contain the dummy task) > [~bolke] -- This message was sent by Atlassian JIRA (v6.3.15#6346)