On Wed, Jun 26, 2019 at 9:45 PM Gerard Toonstra wrote:
>
> That's not my experience of how SLA's work at the moment. I've observed
> this to currrently work as:
>
> 1. An SLA is configured as the "time delta" after some dag execution
> schedule.
> 2. The SLA is configured at task level, so any ta
That's not my experience of how SLA's work at the moment. I've observed
this to currrently work as:
1. An SLA is configured as the "time delta" after some dag execution
schedule.
2. The SLA is configured at task level, so any tasks still running or need
to run after "time delta" will be aggregated
Hi all,
I'm looking to get some clarity on the intended behavior for
SLAs. This has come up several times in the past, but as far as I can
tell there hasn't been a definitive answer. As pointed out in
https://issues.apache.org/jira/browse/AIRFLOW-249 (open for several
years now):
the SLA logi
