You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "r11234 (via GitHub)" <gi...@apache.org> on 2024/11/08 10:41:19 UTC
[D] Extra link is not visible when using `TriggerDagRunOperator` inside a `task` [airflow]
GitHub user r11234 created a discussion: Extra link is not visible when using `TriggerDagRunOperator` inside a `task`
I have the following setup:
```python
@task(task_id="example_task")
def example_task(arg1, arg2, **kwargs):
TriggerDagRunOperator(
task_id="..."
trigger_dag_id="..."
conf = { ... } # depends on arg1 and arg2
).execute(kwargs)
```
The issue I face is that I don't see the "Triggered DAG" extra link in the UI when I use example_task in a DAG. Is there a fix for this?
GitHub link: https://github.com/apache/airflow/discussions/43815
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Extra link is not visible when using `TriggerDagRunOperator` inside a `task` [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk added a comment to the discussion: Extra link is not visible when using `TriggerDagRunOperator` inside a `task`
Yes you cannot use "classic" operator in "task flow one". Use either one or the other. It literally makes no sense to wrap a classic task with taskflow. See the docs on how you can combine some tasks written in task flow way with some other tasks written in "classic way". There are examples.
GitHub link: https://github.com/apache/airflow/discussions/43815#discussioncomment-11191597
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org