[jira] [Commented] (AIRFLOW-642) Add dag_run to the task_instance table or create new taskuuid column and use this to uniquely identify a task

["Daniel Imberman (Jira)" <ji...@apache.org>]

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

Daniel Imberman commented on AIRFLOW-642:
-----------------------------------------

This ticket has been moved to https://github.com/apache/airflow/issues/7968


>  Add dag_run to the task_instance table or create new taskuuid column 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
>            Priority: Major
>
> 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
(v8.3.4#803005)