[
https://issues.apache.org/jira/browse/AIRFLOW-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742015#comment-16742015
]
ASF subversion and git services commented on AIRFLOW-3690:
----------------------------------------------------------
Commit 0d386e29d87ce1f8c8528c16a7cf4cbc15d70b43 in airflow's branch
refs/heads/dont-bake-env-into-tmp-config from Xiaodong
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=0d386e2 ]
[AIRFLOW-3690] Fix bug to set state of a task for manually-triggered DAGs
(#4504)
> Fix api.common.experimental.mark_tasks.set_state for 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
> Priority: Major
> Fix For: 1.10.2
>
>
> Line
> [https://github.com/apache/airflow/pull/2085/files#diff-4a8a799d7af166d79e74a8a3587e6171R75|https://github.com/apache/airflow/pull/2085/files#diff-4a8a799d7af166d79e74a8a3587e6171R75,]
> removes microsecond 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 microsecond 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 microsecond in their
> execution_date is 0.
>
> Actually someone already reported this in the original GitHub PR:
> [https://github.com/apache/airflow/pull/2085#issuecomment-297713635]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
