tomrutter commented on issue #39118:
URL: https://github.com/apache/airflow/issues/39118#issuecomment-2080433343
Happy to be assigned, but if someone has a clear idea, happy for that to go
ahead too.
I’m guessing the big issue with rendering on the webserver is picking up the
raphaelauv commented on issue #39118:
URL: https://github.com/apache/airflow/issues/39118#issuecomment-2079827043
since we can define at operator definition the field `map_index_template="{{
task.op_kwargs['date'] }}",`, it can be render by the webserver
--
This is an automated message
RNHTTR commented on issue #39118:
URL: https://github.com/apache/airflow/issues/39118#issuecomment-2079818129
@tomrutter Would you like to be assigned?
Given the current design (using a task's `context` object) I think this
might be trickier than meets the eye.
--
This is an
raphaelauv commented on issue #39118:
URL: https://github.com/apache/airflow/issues/39118#issuecomment-2066707639
related : https://github.com/apache/airflow/issues/39092
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
tomrutter commented on issue #39118:
URL: https://github.com/apache/airflow/issues/39118#issuecomment-2064346195
This is a follow on from #39065 with a narrower scope (just rendering while
the task is running) as the other items in that issue have been or will be
resolved by the other
tomrutter opened a new issue, #39118:
URL: https://github.com/apache/airflow/issues/39118
### Description
The map_index_template field on a task is used to render a custom name for
each individual sub task in a mapped task. It is generated by rendering the
task context on the jinja
