Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Daniel Standish
gt; >>> >> > > >>> >>> Late to the party, but I'd vote for `DeadlineReference` too. > > Concise > > >>> and > > >>> >>> does the job well. > > >>> >>> > > >>> >>>

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Ferruzzi, Dennis
rface so users can add their own as long as it returns a datetime and a callback, they can conceivably make it monitor whatever they want. But so far my plans have been entirely time-based, either dynamically ("one hour after the last run finished") or static ("every day before the

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Jarek Potiuk
ell. > >>> >>> > >>> >>> Thanks & Regards, > >>> >>> Amogh Desai > >>> >>> > >>> >>> > >>> >>> On Tue, Feb 25, 2025 at 7:56 AM Wei Lee > wrote: > >>> >>&g

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Daniel Standish
; >>> >>>>> On Feb 25, 2025, at 4:02 AM, Daniel Standish >>> >>>> wrote: >>> >>>>> >>> >>>>> Stewing presently thank you :) >>> >>>>> >>> >>>>> On Mon, Feb 24, 2

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Daniel Standish
you :) >> >>>>> >> >>>>> On Mon, Feb 24, 2025 at 11:53 AM Ferruzzi, Dennis >> >>>>> wrote: >> >>>>> >> >>>>>> Alright then. DeadlineReference gets the green light for now! If >> >>>

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Daniel Standish
b 24, 2025 at 11:53 AM Ferruzzi, Dennis > >>>>> wrote: > >>>>> > >>>>>> Alright then. DeadlineReference gets the green light for now! If > >>>> anyone > >>>>>> has a suggestion they like more, please feel free to drop it in > >> here. > >>&

Re: Two Hard Things: Deadline Alerts Edition

2025-02-25 Thread Ash Berlin-Taylor
een light for now! If >>>> anyone >>>>>> has a suggestion they like more, please feel free to drop it in >> here. >>>> I'm >>>>>> working on some Ariflow3.0 stuff before I get back to this, so >> there's >>>>>>

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Ankit Chaurasia
gt; > I'm > > > >> working on some Ariflow3.0 stuff before I get back to this, so > there's > > > >> plenty of time before this is set down if anyone wants to stew on > it a > > > bit. > > > >> > > > >> Thanks for the thoughts, all! > >

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Pavankumar Gopidesu
gt; I'm > > >> working on some Ariflow3.0 stuff before I get back to this, so there's > > >> plenty of time before this is set down if anyone wants to stew on it a > > bit. > > >> > > >> Thanks for the thoughts, all! > > >> > &g

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Amogh Desai
ks for the thoughts, all! > >> > >> > >> - ferruzzi > >> > >> > >> > >> From: Jarek Potiuk > >> Sent: Monday, February 24, 2025 11:11 AM > >> To: dev@airflow.apache.org > >>

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Wei Lee
>> >> Thanks for the thoughts, all! >> >> >> - ferruzzi >> >> >> >> From: Jarek Potiuk >> Sent: Monday, February 24, 2025 11:11 AM >> To: dev@airflow.apache.org >> Subject: RE: [EXT] Two Hard Thi

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Daniel Standish
11:11 AM > To: dev@airflow.apache.org > Subject: RE: [EXT] Two Hard Things: Deadline Alerts Edition > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. &g

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Ferruzzi, Dennis
n it a bit. Thanks for the thoughts, all! - ferruzzi From: Jarek Potiuk Sent: Monday, February 24, 2025 11:11 AM To: dev@airflow.apache.org Subject: RE: [EXT] Two Hard Things: Deadline Alerts Edition CAUTION: This email originated from outside of the organi

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Jarek Potiuk
Yep. DaeadlineReference is good . On Mon, Feb 24, 2025 at 8:07 PM Mehta, Shubham wrote: > +1 to DeadlineReference. It is clear and allows flexibility to choose any > reference point. > > shubham > > On 2025-02-24, 10:00 AM, "Ferruzzi, Dennis" LID> wrote: > > >

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Mehta, Shubham
+1 to DeadlineReference. It is clear and allows flexibility to choose any reference point. shubham On 2025-02-24, 10:00 AM, "Ferruzzi, Dennis" mailto:ferru...@amazon.com.inva>LID> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments u

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Akash Sharma
How about DeadlineStartPoint or DeadlineStartRef? On Mon, 24 Feb, 2025, 23:46 Tzu-ping Chung, wrote: > I like StartsFrom, but “DeadlineStartsFrom” sounds like when the deadline > is. It should have another word in front. > > DeadlineReference sounds reasonable to me. Something like DeadlineBase

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Vincent Beck
+1 for reference, it reads well and makes sense to me On 2025/02/24 18:15:02 Tzu-ping Chung wrote: > I like StartsFrom, but “DeadlineStartsFrom” sounds like when the deadline is. > It should have another word in front. > > DeadlineReference sounds reasonable to me. Something like DeadlineBase or

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Tzu-ping Chung
I like StartsFrom, but “DeadlineStartsFrom” sounds like when the deadline is. It should have another word in front. DeadlineReference sounds reasonable to me. Something like DeadlineBase or DeadlineBasis could be possible too, although I actually like reference better. I kind of feel DeadlineMe

Re: Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Jarek Potiuk
Why not `DeadlineStartsFrom` ? On Mon, Feb 24, 2025 at 7:00 PM Ferruzzi, Dennis wrote: > Hey folks. I need to narrow down the name for one of the parameters on > the Deadline Alerts work and I'm fishing for suggestions. > > TLDR:need_by_date = {some existing timestamp} + {a user-defined

Two Hard Things: Deadline Alerts Edition

2025-02-24 Thread Ferruzzi, Dennis
Hey folks. I need to narrow down the name for one of the parameters on the Deadline Alerts work and I'm fishing for suggestions. TLDR:need_by_date = {some existing timestamp} + {a user-defined timedelta} The existing timestamp could be dynamic (like when the dagrun is queued or when a spec