potiuk commented on issue #18253:
URL: https://github.com/apache/airflow/issues/18253#issuecomment-924255102
As explained in #18402 I think in most cases you should not change values of
the parameter but you should simply fail the Task if you see that it runs
without the right parameter set. You should FAIL the task rather than mutate it
in this case if it violates the Policy. There are some cases where you would
likely want to mutate the task, but I think vast majority of cases is to fail
it when the Policy is not met.
As opposed to "magic defaults" this has multiple good properties:
* it is very explicit
* it teaches people to use good practices (especially if your exceptions are
informative, provide the user with explanation and guide them how to comply
with the Policy.
* it allows you to make some more fine-grained check for the parameter values
I am converting that issue into discussion - I would like to hear why you
would not be able to use it this way., I see that as non-issue, more of a
choice that the Airflow project made.
--
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]
