Hey kaxil,
I want to let you know there is an issue since 1.10.2rc1 when you
trigger a dag via the Pause/UnPause button. We discussed it here
https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1547855016439700?thread_ts=1547855016.439700&cid=CCQ7EGB1P
Kind regards,
Felix Uellendall
Am 18
Without this unique constraint, how is the scheduler supposed to
find/update the state of each specific TaskInstance or DagRun? How should
the log be named & stored?
It should be there.
XD
On Sat, Jan 19, 2019 at 03:20 Ash Berlin-Taylor wrote:
> So that it's here on a searchable record:
>
> S
So that it's here on a searchable record:
Simply this is how airflow identifies tasks - `airflow run my_dag_id 2018-01-17
my task`.
If you were to have two dag runs for the exact same milliseconds which one
would it run? Much of the system treats this combo as unique, so lots of code
would nee
Hi,
almost a year ago I reported an issue to Airflow's Jira:
https://issues.apache.org/jira/browse/AIRFLOW-2319
Recently, someone pointed out that I should ask here on the mailing list (I
thought I did, but apparently, I did not).
So here's the thing: the DagRun table has a unique constraint on
A friendly reminder to all to test the RC2 and vote.
On 18/01/2019, 17:29, "Kaxil Naik" wrote:
Will do.
On Fri, Jan 18, 2019, 17:23 Ash Berlin-Taylor We shouldn't be publishing MD5 sums anymore - please remove them.
>
> (Cherry pick 55853c3c23fe177bcf4ca19697f1e664325c69e
Will do.
On Fri, Jan 18, 2019, 17:23 Ash Berlin-Taylor We shouldn't be publishing MD5 sums anymore - please remove them.
>
> (Cherry pick 55853c3c23fe177bcf4ca19697f1e664325c69ea to update the script)
>
>
> > On 17 Jan 2019, at 21:57, Kaxil Naik wrote:
> >
> > Hey all,
> >
> > I have cut Airflow
We shouldn't be publishing MD5 sums anymore - please remove them.
(Cherry pick 55853c3c23fe177bcf4ca19697f1e664325c69ea to update the script)
> On 17 Jan 2019, at 21:57, Kaxil Naik wrote:
>
> Hey all,
>
> I have cut Airflow 1.10.2 RC2. This email is calling a vote on the release,
> which will
