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

Posted to commits@airflow.apache.org by "Luke Maycock (JIRA)" <ji...@apache.org> on 2016/11/24 15:14:58 UTC

[jira] [Commented] (AIRFLOW-70) Use dag_run_id in TaskInstances for lineage

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

Luke Maycock commented on AIRFLOW-70:
-------------------------------------

+1

We also find this to be an issue. This issue is similar to https://issues.apache.org/jira/browse/AIRFLOW-642 but the use of a numeric unique identifier is preferable to a string such as dag_run_id.

> Use dag_run_id in TaskInstances for lineage
> -------------------------------------------
>
>                 Key: AIRFLOW-70
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-70
>             Project: Apache Airflow
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: Airflow 1.7.1
>            Reporter: Bolke de Bruin
>             Fix For: Airflow 1.8
>
>




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