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

2020-05-14 Thread Kevin Yang
+1 On Thu, May 14, 2020 at 1:18 PM Dan Davydov wrote: > +1 but in the future I think better would be > /dags/{dag_id}/dagRuns/{execution_date}/{run_number}. That would give an > automatic ordering between two runs, is a lot simpler than > "backfill_2020-03-16T00:00:00+00:00" and helps enable the

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

2020-05-14 Thread Daniel Imberman
+1 for sure! via Newton Mail [https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.50&pv=10.14.6&source=email_footer_2] On Thu, May 14, 2020 at 1:18 PM, Dan Davydov wrote: +1 but in the future I think better would be /dags/{dag_id}/dagRuns/{execution_date}/{run_number}. That would give an automatic

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

2020-05-14 Thread Dan Davydov
+1 but in the future I think better would be /dags/{dag_id}/dagRuns/{execution_date}/{run_number}. That would give an automatic ordering between two runs, is a lot simpler than "backfill_2020-03-16T00:00:00+00:00" and helps enable the multiple dagruns per execution date that you mention. On Thu, M

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

2020-05-14 Thread Jarek Potiuk
+1 On Thu, May 14, 2020 at 4:45 PM Kamil Breguła wrote: > +1 > > > On Wed, May 13, 2020 at 1:10 PM Kaxil Naik wrote: > > > > +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. > > > > >

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

2020-05-14 Thread Kamil Breguła
+1 On Wed, May 13, 2020 at 1:10 PM Kaxil Naik wrote: > > +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 bec

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 c