You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Xiaodong DENG (JIRA)" <ji...@apache.org> on 2019/01/13 06:54:00 UTC
[jira] [Created] (AIRFLOW-3690) Fix "Mark Success/Failed" feature
for the manually-triggered DAG Runs
Xiaodong DENG created AIRFLOW-3690:
--------------------------------------
Summary: Fix "Mark Success/Failed" feature for the manually-triggered DAG Runs
Key: AIRFLOW-3690
URL: https://issues.apache.org/jira/browse/AIRFLOW-3690
Project: Apache Airflow
Issue Type: Bug
Components: api
Reporter: Xiaodong DENG
Assignee: Xiaodong DENG
Line [https://github.com/apache/airflow/pull/2085/files#diff-4a8a799d7af166d79e74a8a3587e6171R75|https://github.com/apache/airflow/pull/2085/files#diff-4a8a799d7af166d79e74a8a3587e6171R75,] removes millisecond information from the execution_date in the set_state function. But this will fail the query when it tries to look for all th valid execution_dates in the database, because millisecond is stored in the database.
The result is: for all the manually-triggered DAG Runs, if users try to mark state of a task instance, it will fail because no corresponding records can be found.
This doesn't impact any scheduled DAG Runs since the millisecond in their execution_date is 0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)