What about Dask Executor as well. On Fri, Jan 25, 2019, 16:35 Daniel Imberman <daniel.imber...@gmail.com wrote:
> @sid basically my response lol > > I haven't seen any emails from any users and if it's been broken for two > versions then there doesn't seem to be enough interest to maintain it. > > On Fri, Jan 25, 2019, 8:27 AM Sid Anand <r39...@gmail.com> wrote: > > > LOL :_0 > > -s > > > > On Fri, Jan 25, 2019 at 8:25 AM Bolke de Bruin <bdbr...@gmail.com> > wrote: > > > > > I agree. Maybe we should make a choice on what we consider 1st class > > > executors and move others to contrib (I'm looking at you celery) > > > > > > Sent from my iPhone > > > > > > > On 25 Jan 2019, at 12:46, Ash Berlin-Taylor <a...@apache.org> wrote: > > > > > > > > Is anyone using the Mesos Executor? I think we should deprecate and > > > remove it. > > > > > > > > The reason I say that is I have a feeling it's been broken since > 1.9.0 > > > and no-one has noticed: > > > > > > > > class MesosExecutor(BaseExecutor, LoginMixin): > > > > > > > > def start(self): > > > > # ... > > > > self.log.info( > > > > 'MesosFramework master : %s, name : %s, cpu : %s, mem : > %s, > > > checkpoint : %s', > > > > master, framework.name, > > > > str(task_cpu), str(task_memory), str(framework.checkpoint) > > > > ) > > > > > > > > > > > > That mixin should have been LoggingMixin, not LoginMixin. But given > > this > > > bug has been in since > > > > > > https://github.com/apache/airflow/commit/a7a518902dcf1e7fd4bf477cf57cee691f181b29 > > > which was in the 1.9.0 release I propose we simply remove this executor > > > from master. > > > > > > > > Thoughts? > > > > > > > > Ash > > > > > >
