[
https://issues.apache.org/jira/browse/AIRFLOW-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042004#comment-16042004
]
kenneth lam commented on AIRFLOW-1293:
--------------------------------------
the ability to generate the task name on the fly is important as a lot of the
cases, you will want to "clone" a job to multiple copies with just parameter
differences. Eg. processing of n files , ideally, i can generate n "clones" job
with name like T1~files1 .. T1~filesN
> Dynamically generated dependency job get marked as Removed state automatically
> ------------------------------------------------------------------------------
>
> Key: AIRFLOW-1293
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1293
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: kenneth lam
>
> In the dag, set up two task T1 >> T2.
> while task id of T2 is not static as the task id is based on the ip address
> of the running host.
> As a result, airflow mark T2 as "Removed" and thus can't execute.
> Although the dependency graph is constructed correctly in the web admin page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
