Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread Alex Van Boxel
+1 (binding) Note: we had to revert all our ONE_SUCCESS with ALL_SUCCESS trigger rules where the parent nodes where joining with a SKIP. But I can of should have known this was coming. Apart of that I had a successful run last night. On Tue, Mar 14, 2017 at 1:37 AM siddharth anand wrote: I'm g

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread Maxime Beauchemin
+1 (binding) On Tue, Mar 14, 2017 at 3:59 AM, Alex Van Boxel wrote: > +1 (binding) > > Note: we had to revert all our ONE_SUCCESS with ALL_SUCCESS trigger rules > where the parent nodes where joining with a SKIP. But I can of should have > known this was coming. Apart of that I had a successful

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread siddharth anand
+1 (binding) On Tue, Mar 14, 2017 at 8:42 AM, Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > +1 (binding) > > On Tue, Mar 14, 2017 at 3:59 AM, Alex Van Boxel wrote: > > > +1 (binding) > > > > Note: we had to revert all our ONE_SUCCESS with ALL_SUCCESS trigger rules > > where the paren

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread Daniel Huang
+1 (non-binding)! On Tue, Mar 14, 2017 at 11:35 AM, siddharth anand wrote: > +1 (binding) > > > On Tue, Mar 14, 2017 at 8:42 AM, Maxime Beauchemin < > maximebeauche...@gmail.com> wrote: > > > +1 (binding) > > > > On Tue, Mar 14, 2017 at 3:59 AM, Alex Van Boxel > wrote: > > > > > +1 (binding) >

Make Scheduler More Centralized

2017-03-14 Thread Rui Wang
Hi, The design doc below I created is trying to make airflow scheduler more centralized. Briefly speaking, I propose moving state change of TaskInstance to scheduler. You can see the reasons for this change below. Could you take a look and comment if you see anything does not make sense? -Rui -

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread siddharth anand
FYI, I've just hit a major bug in the release candidate related to "clear task" behavior. I've been running airflow in both stage and prod since yesterday on rc5 and have reproduced this in both environments. I will file a JIRA for this tonight, but wanted to send a note over email as well. In my

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread Ruslan Dautkhanov
`airflow kerberos` is broken in 1.8-rc5 https://issues.apache.org/jira/browse/AIRFLOW-987 Hopefully fix can be part of the 1.8 release. -- Ruslan Dautkhanov On Tue, Mar 14, 2017 at 6:19 PM, siddharth anand wrote: > FYI, > I've just hit a major bug in the release candidate related to "clear t

Re: [VOTE] Release Airflow 1.8.0 based on Airflow 1.8.0rc5

2017-03-14 Thread Bolke de Bruin
That is not an airflow error, but a Kerberos error. Try executing the kinit command on the command line by yourself. Bolke Sent from my iPhone > On 14 Mar 2017, at 23:11, Ruslan Dautkhanov wrote: > > `airflow kerberos` is broken in 1.8-rc5 > https://issues.apache.org/jira/browse/AIRFLOW-987