> > > Do we know how many of those affected operators have "wait=False" by
> > > default? I think that should help us to determine the action.
It's not only about those that are False by default. If the user is specifying
False manually, we are in the same situation.
And we have no idea how often users override the "wait" value with False.
> I would like to propose the following order of precedence:
>
> 1. If wait_for_completion=False, it should ignore what the default_deferrable
> is set to
> and should not wait for completion whether synchronously or
> asynchronously(deferral)
That would be a breaking change compared to what has been done so far. I think
all operators have been implemented with something like
if deferrable:
defer()
elif wait:
poll()
It would only be breaking for operators that have wait=False by default though,
but it might be counter intuitive to have to set 2 booleans to have the
expected behavior.
I think a better way to see it is not a combination of 2 booleans (wait/defer)
like you present it, but of 3 : wait param, defer param and defer config.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
