I think we might need to update the capability matrix with some of the new features that have popped up. Immediate things that come to mind are: * Timer/State API for user DoFns (coupled with new-style DoFn) (not yet completely in master) * SplittableDoFn
This would allow tracking the process in each of these for each runner and would not require hunting for that information in email threads. On Tue, 25 Oct 2016 at 08:12 Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1. For me it's one of the most important point for the new website. We > should give a clear and exhaustive list of what we have, both for runners > and IOs (with supported features). > > Regards > JB > > > > On Oct 24, 2016, 21:52, at 21:52, "Ismaël Mejía" <ieme...@gmail.com> > wrote: > >Hello, > > > >I am really happy to see new runners been contributed to our community > >(e.g. GearPump and Apex recently). We have not discussed a lot about > >the > >current capabilities of both runners. > > > >Following the recent discussion about making ongoing work more explicit > >in > >the mailing list, I would like to ask the people involved about the > >current > >status of them, I think it is important to discuss this (apart of > >creating > >the given JIRAs + updating the capability matrix docs) because more > >people > >can eventually jump and give a hand on open issues. > > > >I remember there was a google doc for the capabilities of each runner, > >is > >this doc still available (sorry I lost the link). I suppose that once > >these > >ongoing runners mature we can add this doc also to the website. > >https://beam.apache.org/learn/runners/capability-matrix/ > > > >Regards, > >Ismaël > > > >ps. @Amit, given that the spark 2 (Dataset based) runner has also a > >feature > >branch, if you consider it worth, can you please share a bit about that > >work too. > > > >ps2. Can anyone please share the link to the google doc I was talking > >about, I can't find it after the recent changes to the website. > > >
