[jira] [Comment Edited] (AIRFLOW-52) Release airflow 1.7.1

["Bolke de Bruin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273778#comment-15273778 ] 

Bolke de Bruin edited comment on AIRFLOW-52 at 5/6/16 2:01 PM:
---------------------------------------------------------------

Please note that we probably have another blocker. Airflow can "lose" queued tasks, ie. tasks in queued state that will never be picked up. I have reproduced this and will report on it shortly.


was (Author: bolke):
Please note that we probably have another blocker. Airflow can "loose" queued tasks, ie. tasks in queued state that will never be picked up. I have reproduced this and will report on it shortly.

> 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 loosing queued tasks (see linked issue)



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