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 5BBDC200C88 for ; Thu, 18 May 2017 08:43:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5A348160BD4; Thu, 18 May 2017 06:43:09 +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 99590160BC4 for ; Thu, 18 May 2017 08:43:08 +0200 (CEST) Received: (qmail 79289 invoked by uid 500); 18 May 2017 06:43:07 -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 79247 invoked by uid 99); 18 May 2017 06:43:07 -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, 18 May 2017 06:43:07 +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 2D4DE18139D for ; Thu, 18 May 2017 06:43:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 kgnotX9VqLhN for ; Thu, 18 May 2017 06:43:06 +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 5D1EE5F523 for ; Thu, 18 May 2017 06:43:05 +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 99738E07E1 for ; Thu, 18 May 2017 06:43:04 +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 57ADE263A4 for ; Thu, 18 May 2017 06:43:04 +0000 (UTC) Date: Thu, 18 May 2017 06:43:04 +0000 (UTC) From: "Michael Shire (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-1223) Is there a (preferred) method for programmatically forcing a dag's refresh MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 18 May 2017 06:43:09 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shire updated AIRFLOW-1223: ----------------------------------- Description: When making a change to a dag, in order to immediately load the change I have to click the "refresh" symbol in the dag list UI. Is there a preferred way to programmatically force a dag to refresh/reload immediately? sample use case: A dag creates tasks and dependencies by reading a table (e.g. a list or a db table). When additions or changes are made to this list, I'd like a command I can run to force the dag to update/refresh/reload straight away to pick up the new tasks and also appear refreshed in the webserver UI. The closest I can find is "airflow initdb" though I do not think that fully covers it and am unclear to the consequences or side effects of a running airflow. was: When making a code change to a dag, in order to immediately load the change I have to click the "refresh" symbol in the dag list UI. Is there a preferred way to programmatically force a dag to refresh/reload immediately? sample use case: A dag creates tasks and dependencies by reading a table (e.g. a list or a db table). When additions or changes are made to this list, I'd like a command I can run to force the dag to update/refresh/reload straight away to pick up the new tasks and also appear refreshed in the webserver UI. The closest I can find is "airflow initdb" though I do not think that fully covers it and am unclear to the consequences or side effects of a running airflow. > Is there a (preferred) method for programmatically forcing a dag's refresh > -------------------------------------------------------------------------- > > Key: AIRFLOW-1223 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1223 > Project: Apache Airflow > Issue Type: Wish > Components: DAG, ui > Affects Versions: Airflow 1.7.1 > Reporter: Michael Shire > > When making a change to a dag, in order to immediately load the change I have to click the "refresh" symbol in the dag list UI. > Is there a preferred way to programmatically force a dag to refresh/reload immediately? > sample use case: > A dag creates tasks and dependencies by reading a table (e.g. a list or a db table). When additions or changes are made to this list, I'd like a command I can run to force the dag to update/refresh/reload straight away to pick up the new tasks and also appear refreshed in the webserver UI. > The closest I can find is "airflow initdb" though I do not think that fully covers it and am unclear to the consequences or side effects of a running airflow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)