airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iuliia Volkova (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-1823) API get_task_info is incompatible with manual runs created by UI
Date Mon, 26 Nov 2018 04:42:00 GMT

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

Iuliia Volkova commented on AIRFLOW-1823:
-----------------------------------------

[~ashb], a ticket is not actual for version 1.10

> API get_task_info is incompatible with manual runs created by UI
> ----------------------------------------------------------------
>
>                 Key: AIRFLOW-1823
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1823
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.0.0
>         Environment: ubuntu
> Airflow 1.9rc02
> commit: https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126
>            Reporter: Jeremy Lewi
>            Assignee: Iuliia Volkova
>            Priority: Minor
>
> The API method [task_instance_info|https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126]
doesn't work with manual runs created by the UI.
> The UI creates dag runs with ids with sub second precision in the name. An example of
a run created by the UI is
> 2017-11-16T20:23:32.045330
> The endpoint for  [task_instance_info|https://github.com/apache/incubator-airflow/blob/master/airflow/www/api/experimental/endpoints.py#L126]
however assumes the dag run id is of the form '%Y-%m-%dT%H:%M:%S'.
> Runs triggered via the CLI generate run ids with the form expected by the API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message