You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/07/13 01:46:36 UTC

[GitHub] [airflow] uranusjr commented on a diff in pull request #25012: Update tutorial docs to include a definition of operators

uranusjr commented on code in PR #25012:
URL: https://github.com/apache/airflow/pull/25012#discussion_r919569319


##########
docs/apache-airflow/tutorial.rst:
##########
@@ -102,11 +102,28 @@ define a ``schedule_interval`` of 1 day for the DAG.
     :start-after: [START instantiate_dag]
     :end-before: [END instantiate_dag]
 
+Operators
+---------
+
+An operator defines a unit of work for Airflow to complete. They are the most basic building blocks of DAGs.
+
+All operators inherit from the BaseOperator, which includes all of the required arguments for

Review Comment:
   > All operators inherit from the BaseOperator
   
   This is kind of technically inaccurate since task-mapping produces operators that do not inherit from BaseOperator.
   
   > They are the most basic building blocks of DAGs.
   
   While this is technically correct, it may confuse some users since using `@task` (taskflow decorators) does not seem to have anything to do with operators (they do create operators behind the scenes, but it’s more of an implementation detail). So I’d probably just say
   
   > An operator defines a unit of work for Airflow to complete. The operator classes all include required arguments for running work in Airflow. […]



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