+1 (non-binding). Looking forward to this one. Shubham
On 2024-04-22, 12:31 AM, "Amogh Desai" <amoghdesai....@gmail.com <mailto:amoghdesai....@gmail.com>> wrote: 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. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. +1 binding. Excited to see this happen! Thanks & Regards, Amogh Desai On Sat, Apr 20, 2024 at 12:11 AM Igor Kholopov <ikholo...@google.com.inva <mailto:ikholo...@google.com.inva>lid> wrote: > +1 (non-binding) > > Great to see this happening, hope we will see more proposals towards making > Airflow more flexible! > > Regards, > Igor > > On Fri, Apr 19, 2024 at 8:10 PM Daniel Standish > <daniel.stand...@astronomer.io.inva > <mailto:daniel.stand...@astronomer.io.inva>lid> wrote: > > > > > > > It doesn’t affect my vote on the API, but I am very strongly against > this > > > one part of the AIP: > > > > … dag_id are namespaced with `<team>:` prefix. > > > This specific part is getting an implementation/code veto from me. We > > made > > > the mistake of overloading one column to store multiple things in > Airflow > > > before, and I’ve dealt with the fallout in other apps in the past. > Trust > > > me: do. not. do. this. > > > > I agree with Ash's sentiment. Is adding a tenant_id or something so > > unpalatable? > > >
