This is an automated email from the ASF dual-hosted git repository.
pankajkoti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 4d5591a509 Provide extra tip on labeling DynamicTaskMapping (#39977)
4d5591a509 is described below
commit 4d5591a509cf9c73f768a8962ddeca3ae6ded10d
Author: fritz-astronomer <80706212+fritz-astrono...@users.noreply.github.com>
AuthorDate: Fri May 31 12:12:44 2024 -0400
Provide extra tip on labeling DynamicTaskMapping (#39977)
* Provide extra tip on labeling DynamicTaskMapping
---
docs/apache-airflow/authoring-and-scheduling/dynamic-task-mapping.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/docs/apache-airflow/authoring-and-scheduling/dynamic-task-mapping.rst
b/docs/apache-airflow/authoring-and-scheduling/dynamic-task-mapping.rst
index dd6f42bc85..8e9fa7bd4d 100644
--- a/docs/apache-airflow/authoring-and-scheduling/dynamic-task-mapping.rst
+++ b/docs/apache-airflow/authoring-and-scheduling/dynamic-task-mapping.rst
@@ -174,7 +174,7 @@ This would result in the add task being called 6 times.
Please note, however, th
Named mapping
-------------
-By default, mapped tasks are assigned an integer index. It is possible to
override the integer index for each mapped task in the Airflow UI with a name
based on the task's input. This is done by providing a Jinja template for the
task with ``map_index_template``. This template is rendered after each expanded
task is executed using the task context. This means you can reference
attributes on the task like this:
+By default, mapped tasks are assigned an integer index. It is possible to
override the integer index for each mapped task in the Airflow UI with a name
based on the task's input. This is done by providing a Jinja template for the
task with ``map_index_template``. This will typically look like
``map_index_template="{{ task.<property> }}"`` when the expansion looks like
``.expand(<property>=...)``. This template is rendered after each expanded task
is executed using the task context. This [...]
.. code-block:: python
