eladkal commented on code in PR #49389:
URL: https://github.com/apache/airflow/pull/49389#discussion_r2048424994


##########
airflow-core/docs/core-concepts/executor/index.rst:
##########
@@ -251,7 +252,7 @@ Mandatory Methods to Implement
 The following methods must be overridden at minimum to have your executor 
supported by Airflow:
 
 * ``sync``: Sync will get called periodically during executor heartbeats. 
Implement this method to update the state of the tasks which the executor knows 
about. Optionally, attempting to execute queued tasks that have been received 
from the scheduler.
-* ``execute_async``: Executes a command asynchronously. A command in this 
context is an Airflow CLI command to run an Airflow task. This method is called 
(after a few layers) during executor heartbeat which is run periodically by the 
scheduler. In practice, this method often just enqueues tasks into an internal 
or external queue of tasks to be run (e.g. ``KubernetesExecutor``). But can 
also execute the tasks directly as well (e.g. ``LocalExecutor``). This will 
depend on the executor.
+* ``execute_async``: Executes a command (Airflow 2) /workload(Airflow 3) 
asynchronously. A command is an Airflow CLI command whereas workload is basic 
unit of work that represents an Airflow task. This method is called (after a 
few layers) during executor heartbeat which is run periodically by the 
scheduler. In practice, this method often just enqueues tasks into an internal 
or external queue of tasks to be run (e.g. ``KubernetesExecutor``). But can 
also execute the tasks directly as well (e.g. ``LocalExecutor``). This will 
depend on the executor.

Review Comment:
   Noting that the docs are versioned. so if someone want to see the content of 
this page in Airflow 2 they can just click the version button



-- 
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-unsubscr...@airflow.apache.org

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

Reply via email to