amoghrajesh commented on code in PR #49389:
URL: https://github.com/apache/airflow/pull/49389#discussion_r2052233762
##########
airflow-core/docs/core-concepts/executor/index.rst:
##########
@@ -49,6 +49,40 @@ If you want to check which executor is currently set, you
can use the ``airflow
LocalExecutor
+Workloads
+---------
+
+A workload in context of an Executor is the fundamental unit of execution for
an executor. It represents a discrete
+operation or job that the executor runs on a worker. For example, it can run
user code encapsulated in an Airflow task
+on a worker.
Review Comment:
Okay let me answer the difference between workload vs ti.
In the context for an executor, both essentially mean the same. This is what
a workload looks like:
```
ExecuteTask(
token="mock",
ti=TaskInstance(
id=UUID("4d828a62-a417-4936-a7a6-2b3fabacecab"),
task_id="mock",
dag_id="mock",
run_id="mock",
try_number=1,
map_index=-1,
pool_slots=1,
queue="default",
priority_weight=1,
executor_config=None,
parent_context_carrier=None,
context_carrier=None,
queued_dttm=None,
),
dag_rel_path=PurePosixPath("mock.py"),
bundle_info=BundleInfo(name="n/a", version="no matter"),
log_path="mock.log",
type="ExecuteTask",
)
```
Workload is an operational unit for running "something" using task sdk
paradigm. For the case of executors, its a `ti` but we also run dag processors,
triggers etc with task sdk and that is when a workload definition changes.
--
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
