potiuk commented on issue #27285:
URL: https://github.com/apache/airflow/issues/27285#issuecomment-1292795423
Following the comment - I have a bold proposal ... It's not exaclty what the
original proposal is, but in a way it provides a possibility to do what was
originally requested here.
Why don't we add an option (disabled by default) to make ALL ELIGIBLE fields
- "templeted_fields" (and automatically .output -capable).
That bothered me for a while but I think there is very little impact of
making all fields templated and often people complained that templated fields.
Performance overhead should be negligible (just walking through parameters and
jinjafying them which in most cases will be no-op).
The only drawback it might have is that the if a string contains " {{}}"
acidentally - this will be replaced with "" - which is backwards-incompatible.
We could also provide a mechanism that would eclude a field from being
templated just in case.
I think that has a number of benefits - for example our users will not have
extend operators that miss some fields in "templated_fields".
I am not too worried anout "outlets" and executor_config not being
available for .output and user's education. As long as we simply error out in
this case that should be good.
In a way it woudl be similar to `render_template_as_native_obj` DAG
paraemeter.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
