[
https://issues.apache.org/jira/browse/AIRFLOW-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130598#comment-17130598
]
ASF GitHub Bot commented on AIRFLOW-6704:
-----------------------------------------
shanit-saha commented on pull request #7324:
URL: https://github.com/apache/airflow/pull/7324#issuecomment-641965564
To add to my above post. It has so been found that when we remove
`execution_date` parameter from the `TriggerDagRunOperator` it works. Is that a
problem or change in the syntax. Also the Airflow-Dag examples provided with
Airflow1.10.10 repository does not have a sample code for `TriggerDagOperator`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> TaskInstance.operator is not set when task is marked success or failed in the
> Web UI
> ------------------------------------------------------------------------------------
>
> Key: AIRFLOW-6704
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6704
> Project: Apache Airflow
> Issue Type: Bug
> Components: models
> Affects Versions: 1.10.7
> Reporter: Qian Yu
> Assignee: Qian Yu
> Priority: Major
> Fix For: 1.10.10
>
>
> {{TaskInstance.operator}} is currently only set when task is executed. But if
> a task is marked success or failed, the {{operator}} field is left as
> {{None}}.
> This causes bugs when some code tries to use the operator field to find the
> name of the class.
> The fix is trivial, just set {{TaskInstance.operator}} in its constructor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
