You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Sergio Kef (Jira)" <ji...@apache.org> on 2019/09/28 19:14:00 UTC
[jira] [Commented] (AIRFLOW-3553) Microseconds in manually
triggered tasks break "mark as success"
[ https://issues.apache.org/jira/browse/AIRFLOW-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940137#comment-16940137 ]
Sergio Kef commented on AIRFLOW-3553:
-------------------------------------
This is a known issue due to the difference of timestamps between airflow and various rdbms
> Microseconds in manually triggered tasks break "mark as success"
> -----------------------------------------------------------------
>
> Key: AIRFLOW-3553
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3553
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: 1.9.0, 1.10.1, 2.0.0
> Reporter: Jozef Fekiac
> Priority: Major
>
>
> If a user wants to mark success on a dagRun with microseconds (I.e. manually triggered from GUI), user can't mark tasks as success.
>
> in 1.9, replace microseconds is a default behaviour, as per code, but
> [https://github.com/apache/incubator-airflow/blob/v1-9-stable/airflow/www/views.py#L915]
> doesn't handle the microseconds, setting run_id
> propagating it to
> [https://github.com/apache/incubator-airflow/blob/v1-9-stable/airflow/api/common/experimental/trigger_dag.py#L37]
> resulting in no run_id alteration, => it's with microseconds, disabling the "mark as success function" from GUI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)