[
https://issues.apache.org/jira/browse/AIRFLOW-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851901#comment-16851901
]
jack commented on AIRFLOW-1293:
-------------------------------
Not sure what is the issue here.
You can create tasks dynamically for example:
{code:java}
for i in range(5, 0, -1):
t = BashOperator( task_id='Process_File_-{}'.format(i), ... )
{code}
Each task can handle different file from 1 to N.
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)
