You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Arunprasad (JIRA)" <ji...@apache.org> on 2016/11/22 00:48:58 UTC

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

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

Arunprasad edited comment on AIRFLOW-642 at 11/22/16 12:48 AM:
---------------------------------------------------------------

cc  [~criccomini] [~dhaval2025]


was (Author: arunprasadnitt):
cc  [~criccomini]

>  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
>
> 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)