Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Fri, 6 May 2016 16:28:13 +0000 (UTC)
From: "Jeremiah Lowin (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12965341.1462471729000.129810.1462552093011@Atlassian.JIRA>
In-Reply-To: <JIRA.12965341.1462471729000@Atlassian.JIRA>
References: <JIRA.12965341.1462471729000@Atlassian.JIRA> <JIRA.12965341.1462471729672@arcas>
Subject: [jira] [Updated] (AIRFLOW-52) Release airflow 1.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 06 May 2016 16:28:18 -0000


     [ https://issues.apache.org/jira/browse/AIRFLOW-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremiah Lowin updated AIRFLOW-52:
----------------------------------
    Description: 
Release the airflow 1.7.1 tag.

Current status:
There are three issues blocking this release caused by this commit:
https://github.com/apache/incubator-airflow/commit/fb0c5775cda4f84c07d8d5c0e6277fc387c172e6
1. DAGs with a lot of tasks take much longer to parse (~25x slowdown)
2. The following kind of patterns fail:
{code}
email.set_upstream(dag.roots)
dag.add_task(email)
{code}
This is because set_upstream now calls add_task and a task can't be added more than once.

I'm working with the owner of the commit to resolve these issues.

The way to catch (1) in the future is an integration test that asserts a given non-trivial DAG parses under X seconds.
3. Airflow losing queued tasks (see linked issue)

  was:
Release the airflow 1.7.1 tag.

Current status:
There are three issues blocking this release caused by this commit:
https://github.com/apache/incubator-airflow/commit/fb0c5775cda4f84c07d8d5c0e6277fc387c172e6
1. DAGs with a lot of tasks take much longer to parse (~25x slowdown)
2. The following kind of patterns fail:
{code}
email.set_upstream(dag.roots)
dag.add_task(email)
{code}
This is because set_upstream now calls add_task and a task can't be added more than once.

I'm working with the owner of the commit to resolve these issues.

The way to catch (1) in the future is an integration test that asserts a given non-trivial DAG parses under X seconds.
3. Airflow loosing queued tasks (see linked issue)


> Release airflow 1.7.1
> ---------------------
>
>                 Key: AIRFLOW-52
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-52
>             Project: Apache Airflow
>          Issue Type: Task
>          Components: ease
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>              Labels: release
>
> Release the airflow 1.7.1 tag.
> Current status:
> There are three issues blocking this release caused by this commit:
> https://github.com/apache/incubator-airflow/commit/fb0c5775cda4f84c07d8d5c0e6277fc387c172e6
> 1. DAGs with a lot of tasks take much longer to parse (~25x slowdown)
> 2. The following kind of patterns fail:
> {code}
> email.set_upstream(dag.roots)
> dag.add_task(email)
> {code}
> This is because set_upstream now calls add_task and a task can't be added more than once.
> I'm working with the owner of the commit to resolve these issues.
> The way to catch (1) in the future is an integration test that asserts a given non-trivial DAG parses under X seconds.
> 3. Airflow losing queued tasks (see linked issue)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)