airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Kumpan (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRFLOW-5860) Add the field `dagrun_id` to the response of experimental API on trigger.
Date Fri, 08 Nov 2019 03:17:00 GMT

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

Anton Kumpan edited comment on AIRFLOW-5860 at 11/8/19 3:16 AM:
----------------------------------------------------------------

I believe this is duplicate of 

https://issues.apache.org/jira/browse/AIRFLOW-5590

 

Also, even after adding dag_id to the response - it is not useful - because currently date
is used as identifier. It is not really comfortable - so I have https://issues.apache.org/jira/browse/AIRFLOW-5593 as
suggestion. You can work on it if you want


was (Author: akumpan):
I believe this is duplicate of 

https://issues.apache.org/jira/browse/AIRFLOW-5590

> Add the field `dagrun_id` to the response of experimental API on trigger.
> -------------------------------------------------------------------------
>
>                 Key: AIRFLOW-5860
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5860
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: api, cli
>    Affects Versions: 1.10.6
>            Reporter: Douglas Mendez
>            Priority: Major
>
> We are using experimental REST API for automating Airflow Dag, triggering Dags from one
of our microservices. It would be great for us to have within the API response the dagrun_id
to keep track of it with ease.
>  
>  
> *Response example*
>  
> {code:java}
> // code placeholder
> {
>    'execution_date': execution_date, 
>    'message': message, 
>    'dagrun_id': 'dagrun_id
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message