potiuk commented on issue #35542:
URL: https://github.com/apache/airflow/issues/35542#issuecomment-1806466044
Not that I am aware of. But you are welcome to mae PR.
Also I would appreciate you do not try to hijack one thread for other
things. Hopefully someone will answer on the other
ginwakeup commented on issue #35542:
URL: https://github.com/apache/airflow/issues/35542#issuecomment-1806433765
@potiuk is there any other way this can be done at the moment?
It seems from documentation that I should be able to use
`task_instance_mutation_hook` in airflow_local_sett
potiuk commented on issue #35542:
URL: https://github.com/apache/airflow/issues/35542#issuecomment-1806186017
Just to repeat what was there - this is not possible by definition. JINJA
templated fields are resolved after task started (which is after queue was used
to start the task in the
ginwakeup commented on issue #35542:
URL: https://github.com/apache/airflow/issues/35542#issuecomment-1805971367
> I had the same observation some time ago which went into discussion #32471
>
> I proposed to implement an improvement because we have the same demand.
>
> Neverthel
jscheffl commented on issue #35542:
URL: https://github.com/apache/airflow/issues/35542#issuecomment-1804821868
I had the same observation some time ago which went into discussion
https://github.com/apache/airflow/discussions/32471
I proposed to implement an improvement because we hav
ginwakeup opened a new issue, #35542:
URL: https://github.com/apache/airflow/issues/35542
### Description
It is not possible at the moment to dynamically re-route tasks depending on
the DAG Parameters.
An example:
```
@task
def helloWorld():
print("Hello World!"
