I would love to try to join any meetings if you add me. My calendar is too chaotic to be useful on the when2meet :-) but I can often move things around.
Kenn On Wed, Jun 8, 2022 at 2:50 PM Brian Hulette <bhule...@google.com> wrote: > Thanks for reaching out, Ryan, this sounds really cool. I added my > availability to the calendar since I'm interested in this space, but I'm > not sure I can offer much help - I don't have any experience building a > runner, to date I've worked exclusively on the SDK side of Beam. So I hope > some other folks can join as well :) > > @Pablo Estrada <pabl...@google.com> might have some useful insight - he's > been working on a spike to build a Ray runner. > > > On Wed, Jun 8, 2022 at 12:53 PM Robert Bradshaw <rober...@google.com> > wrote: > >> This sounds like a great project. Unfortunately I wouldn't be able to >> meet next week, but would be happy to meet some other time and if that >> doesn't work answer questions over email, etc. Looking forward to a >> Dask runner. >> >> On Wed, Jun 8, 2022 at 9:04 AM Ryan Abernathey >> <ryan.abernat...@gmail.com> wrote: >> > >> > Dear Beamer, >> > >> > Thank you for all of your work on this amazing project. I am new to >> Beam and am quite excited about its potential to help with some data >> processing challenges in my field of climate science. >> > >> > Our community is interested in running Beam on Dask Distributed >> clusters, which we already know how to deploy. This has been discussed at >> https://issues.apache.org/jira/browse/BEAM-5336 and >> https://github.com/apache/beam/issues/18962. It seems technically >> feasible. >> > >> > We are trying to organize a meeting next week to kickstart and >> coordinate this effort. It would be great if we could entrain some Beam >> maintainers into this meeting. If you have interest in this topic and are >> available next week, please share your availability here - >> https://www.when2meet.com/?15861604-jLnA4 >> > >> > Alternatively, if you have any guidance or suggestions you wish to >> provide by email or GitHub discussion, we welcome your input. >> > >> > Thanks again for your open source work. >> > >> > Best, >> > Ryan Abernathey >> > >> >
