Re: What's coming in Airflow 2.0 =- this Wednesday at NYC Online Meetup

2020-05-13 Thread Jarek Potiuk
Thanks! Indeed :), I think the best part was that we could do it together :). J. On Thu, May 14, 2020 at 4:19 AM Kaxil Naik wrote: > Thank You Maxime :) > > On Thu, May 14, 2020, 02:12 Maxime Beauchemin > wrote: > >> I was bummed about not being able to make live today, but found that the >>

Re: What's coming in Airflow 2.0 =- this Wednesday at NYC Online Meetup

2020-05-13 Thread Kaxil Naik
Thank You Maxime :) On Thu, May 14, 2020, 02:12 Maxime Beauchemin wrote: > I was bummed about not being able to make live today, but found that the > video is available already and was able to watch it just now. > https://www.crowdcast.io/e/whats-coming-airflow-2 > > Amazing work presenters and

Re: What's coming in Airflow 2.0 =- this Wednesday at NYC Online Meetup

2020-05-13 Thread Maxime Beauchemin
I was bummed about not being able to make live today, but found that the video is available already and was able to watch it just now. https://www.crowdcast.io/e/whats-coming-airflow-2 Amazing work presenters and committers! It's fantastic to see all of this coming together. Max On Mon, May 11,

Re: Proposal: Change TI from having execution date to dag_run_id (in API at least)

2020-05-13 Thread Kaxil Naik
+1 On Wed, May 13, 2020 at 11:54 AM Ash Berlin-Taylor wrote: > Hi all, > > The discussion about API spec made me think of something. > > Right now the primary key on TI is (dag_id, task_id, exeuction_date). > This is because when Airflow was original written, DagRun didn't exist > as a concept,

Proposal: Change TI from having execution date to dag_run_id (in API at least)

2020-05-13 Thread Ash Berlin-Taylor
Hi all, The discussion about API spec made me think of something. Right now the primary key on TI is (dag_id, task_id, exeuction_date). This is because when Airflow was original written, DagRun didn't exist as a concept, so this was the natural PK. Then DagRun was added with a couple of unique