airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arunprasad (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AIRFLOW-642) Add dag_run to the task_instance table or add taskUUID and use this to uniquely identify a task
Date Mon, 21 Nov 2016 18:36:00 GMT
Arunprasad created AIRFLOW-642:
----------------------------------

             Summary:  Add dag_run to the task_instance table or add taskUUID and use this
to uniquely identify a task
                 Key: AIRFLOW-642
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-642
             Project: Apache Airflow
          Issue Type: Improvement
          Components: DagRun, scheduler
            Reporter: Arunprasad


We are planning to run around 40,000 tasks a day using airflow and some of them are critical
to give quick feedback to developers. 

Currently having execution date to uniquely identify tasks does not work for us since we mainly
trigger dags (instead of running them on schedule) we collide with 1 sec granularity on several
occasions.  Having a task uuid or associating dag_run to task_instance  table and using this
for scheduling and updating status will help us here.



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

Mime
View raw message