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 E2DF8200C1A for ; Mon, 13 Feb 2017 20:11:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DE710160B60; Mon, 13 Feb 2017 19:11: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 307A5160B4A for ; Mon, 13 Feb 2017 20:11:49 +0100 (CET) Received: (qmail 34556 invoked by uid 500); 13 Feb 2017 19:11:48 -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 34545 invoked by uid 99); 13 Feb 2017 19:11:48 -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, 13 Feb 2017 19:11:48 +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 D4189C0185 for ; Mon, 13 Feb 2017 19:11:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id YY44TTq8gC87 for ; Mon, 13 Feb 2017 19:11:47 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 9E8305F47E for ; Mon, 13 Feb 2017 19:11: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 F267CE023B for ; Mon, 13 Feb 2017 19:11:41 +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 AF87321D64 for ; Mon, 13 Feb 2017 19:11:41 +0000 (UTC) Date: Mon, 13 Feb 2017 19:11:41 +0000 (UTC) From: "Yi Chen (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-870) Airflow Web UI "Mark Success" action not working properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Feb 2017 19:11:50 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864239#comment-15864239 ] Yi Chen commented on AIRFLOW-870: --------------------------------- i have opened a PR [https://github.com/apache/incubator-airflow/pull/2075] for issue 1. I think I need a bit more discussion on issue 2. > Airflow Web UI "Mark Success" action not working properly > --------------------------------------------------------- > > Key: AIRFLOW-870 > URL: https://issues.apache.org/jira/browse/AIRFLOW-870 > Project: Apache Airflow > Issue Type: Bug > Affects Versions: Airflow 1.8 > Reporter: Yi Chen > Original Estimate: 168h > Remaining Estimate: 168h > > I have found a few issues and some ideas of resolving them: > 1) *Issue*: In Web UI, if click Mark Success of a task that has not been processed(a.k.a any white box in list view), I get "No task instances to mark as successful" error message. > *Reason*: A task that has not been processed has a record in the table task_instance with state column value as NULL. Then, here https://github.com/apache/incubator-airflow/blob/v1-8-stable/airflow/www/views.py#L1146 , this line filters out not only the case `TI.state = State.SUCCESS` but also the case `TI.state is NULL`. > *Solution*: make this line as ` or_((TI.state.is_(None)), TI.state != State.SUCCESS)).all()` > 2) *Issue*: Not clear why we need a new option in "Mark Success" -- the "Recursive" option. I think we used to have the option "DownStream" or "UpStream" with recursive searching. Can anyone explain the design and double check the implementation? Right now, if I do not choose "Recursive" option with the "DownStream". I get KeyError in this line https://github.com/apache/incubator-airflow/blob/v1-8-stable/airflow/www/views.py#L1188. > *Reason*: In this line, https://github.com/apache/incubator-airflow/blob/v1-8-stable/airflow/www/views.py#L1122 , We actually have got the relatives from recursive searching already, and the task_ids is populated, but task_id_to_dag is not populated properly if "Recursive" option is not chosen. Therefore a KeyError show up later as mentioned above. > *Solution*: I think we have to discuss the design of the desired behavior of each option and refactor code w.r.t.the design. > [This is my first Apache JIRA ticket. Feel free to point out any mistakes in reporting and describing issues if I have any.] -- This message was sent by Atlassian JIRA (v6.3.15#6346)