You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "matthieucx (via GitHub)" <gi...@apache.org> on 2023/07/16 11:15:52 UTC

[GitHub] [airflow] matthieucx commented on issue #32603: Issue when passing the output of a traditional operator to a Task Group

matthieucx commented on issue #32603:
URL: https://github.com/apache/airflow/issues/32603#issuecomment-1637056115

   Thanks a lot for the correction.
   
   To anyone who ends up here having a similar issue, from what I understand:
   
   When you create a `@task()` decorated function, you create a new task template.
   When you call the function inside tha dag context, you create a task.
   
   When you call a traditional operator, you directly create a task, which is why you have to call the operator in the DAG context.
   
   Those are relevant :
   [Tasks Doc](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/tasks.html#tasks)
   [Operators Doc](https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/operators.html#operators)
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org