[
https://issues.apache.org/jira/browse/AIRFLOW-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798047#comment-16798047
]
ASF subversion and git services commented on AIRFLOW-4070:
----------------------------------------------------------
Commit 04f791d7d279871677be87382aa7cf74eb4198a0 in airflow's branch
refs/heads/v1-10-stable from Newton Le
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=04f791d ]
[AIRFLOW-4070] AirflowException -> log.warning for duplicate task dependencies
(#4904)
* [AIRFLOW-4070] log.warning for duplicate task dependencies
This change logs a warning on duplicate task dependencies rather than
raising an AirflowException. This will allow automated task
dependencies to be generated while giving the user the option to
explicitly define task dependencies.
* remove test_duplicate_dependencies
> AirflowException on repeated dependencies prevents automated dependencies
> -------------------------------------------------------------------------
>
> Key: AIRFLOW-4070
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4070
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Newton Le
> Assignee: Newton Le
> Priority: Major
> Fix For: 1.10.3
>
>
> We are trying to build automated dependencies based on data. For example, if
> Task A requires data from Task B, then a task dependency will be
> automatically generated. At the same time, we still want to allow users to
> specify explicit dependencies, e.g. `task_a >> task_b`.
> Airflow's current way of raising an exception on duplicate dependencies
> currently blocks this implementation. Also, I can't think of a good
> justification for it. For the purposes I can imagine, logging a warning seems
> more than sufficient.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
