I made some comments - I think naming is crucial and probably we culd make it more 'use case' than 'low-level' from the user point of view (and likely it won't change much of the idea there).
pon., 23 wrz 2024, 14:06 użytkownik Ferruzzi, Dennis <ferru...@amazon.com.invalid> napisał: > The old SLA feature has been removed in Airflow 3.0 (PR here< > https://github.com/apache/airflow/pull/42285>) and in 3.1 it will be > replaced with Airflow Alerts. Since AIP-57 has been abandoned, this > proposal will replace and supersede AIP-57. That AIP and the discussion > around it are not to be considered as part of this proposal and, unless > mentioned in this new AIP, nothing in those discussions or that AIP is > considered to be part of this one. > > > One of the main points of contention of the SLA feature revolves around > when you start counting. If you set an SLA of "1 hour", is that one hour > after it was scheduled, one hour after it starts running, one hour after it > was queued, or something else entirely. This leads to frequent questions > and confusion. This AIP revolves around the idea of allowing the user to > define that starting point and treat the new SLA-replacement as a > calculated "need-by date". To avoid confusion, the new feature will be > referred to as Alerts rather than SLA and the implementation will allow a > much more versatile experience for the user. > > AIP-86: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 > > > - ferruzzi >
