airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Lamblin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3191) Fix not being able to specify execution_date when creating dagrun
Date Mon, 29 Oct 2018 07:21:00 GMT

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

Daniel Lamblin commented on AIRFLOW-3191:
-----------------------------------------

I can confirm this is an issue and that the PR fixes it.
There is a work around of using the trigger api call instead of trying to create a dagrun
in the UI.

> Fix not being able to specify execution_date when creating dagrun
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-3191
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3191
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: webserver
>    Affects Versions: 1.10.0
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>            Priority: Major
>
> Creating a dagrun using the flask web UI is not possible because execution_date is hidden.
This is because the column type is actually DATETIME where Flask only has a converter for
DateTime (it's the same type, it's a casing issue).
> Fix is to add a form override: form_overrides = dict(execution_date=DateTimeField)
> Only applies to the non-rbac webserver.



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

Mime
View raw message