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

Dan Davydov commented on AIRFLOW-52:
------------------------------------

Update: I'm almost ready to stage the new version, right now I'm hitting one 
last newly introduced exception (same issue as the previous exception of 
calling add_tasks twice) and I've reached out to the owner to help fix it:
AirflowException: Tried to create relationships between tasks that don't have 
DAGs yet. Set the DAG for at least one task  and try again

> 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.
> -3. Airflow losing queued tasks (see linked issue)-
> 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



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

Reply via email to