I think 1.10 is a good idea. I'm working on this refactoring of the sensor structure: https://github.com/apache/incubator-airflow/pull/2875
Would be awesome to get this in. At my current project we use sensors in a few places, but still there is some work to be done. For example, don't allocate an executor slot to the sensors, but have a more sophisticated way of poking. Cheers, Fokko 2018-01-12 21:19 GMT+01:00 Chris Riccomini <[email protected]>: > Just the operator (AIRFLOW-1517) > > On Fri, Jan 12, 2018 at 11:21 AM, Anirudh Ramanathan < > [email protected]> wrote: > > > Sounds awesome. Is k8s support here referring to both the executor and > the > > operator? > > > > Thanks, > > > > > > On Jan 12, 2018 11:18 AM, "Sid Anand" <[email protected]> wrote: > > > > > +1 > > > > > > > > > On Fri, Jan 12, 2018 at 10:56 AM, Chris Riccomini < > [email protected] > > > > > > wrote: > > > > > > > Hey all, > > > > > > > > After some past discussion on Airflow 1.10 vs 2.0, I think we've > > > converged > > > > on a 1.10 as the next step. 1.10 will include: > > > > > > > > * Timezone changes > > > > * Kubernetes support > > > > * New UI > > > > > > > > The first two have been merged in, as I saw Bolke just merged K8s (I > > saw > > > a > > > > few follow-on patches coming, though), and I think the new UI is > > > probably a > > > > couple of weeks out from a PR on master. > > > > > > > > What do people think of starting the release process on master in > Feb? > > > > Given that it took a month last time, I expect 1.10 to be released in > > > > March. Thoughts? > > > > > > > > Cheers, > > > > Chris > > > > > > > > > >
