[
https://issues.apache.org/jira/browse/AIRFLOW-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16768078#comment-16768078
]
jack commented on AIRFLOW-642:
------------------------------
There is pending PR for this [https://github.com/apache/airflow/pull/3210]
with ticket
https://issues.apache.org/jira/browse/AIRFLOW-2307
> 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
(v7.6.3#76005)
