Re: [DISCUSS] Current ongoing work on runners

Good idea. Regards JB ⁣​ On Oct 25, 2016, 17:57, at 17:57, Aljoscha Krettek wrote: >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

Re: [DISCUSS] Current ongoing work on runners

We usually have docs sitting together with the source codes such that each release has its own versioned docs. If the capability matrix is like other codes, we can update it as we add new features. It also applies to other docs like new IO. We could make it a requirement in the PR template.

Re: [DISCUSS] Current ongoing work on runners

SparkRunner status: V1 (Spark 1.6.x - DStream/RDD API): *Batch*: Full model support for batch, continuous ROS testing setup is in process now so that CI will validate constantly. *Streaming*: Supporting UnboundedSource is in review , starting to

Re: [DISCUSS] Current ongoing work on runners

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

Re: [DISCUSS] Current ongoing work on runners

+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" wrote: >Hello, > >I am really

Re: [DISCUSS] Current ongoing work on runners

I think it would be worth publishing a compatibility matrix, if not on the main site, as part of the branch itself. Even better would be if the compatibility matrix was automatically deduced based on a suite of tests that each runner could (attempt to) pass. On Mon, Oct 24, 2016 at 12:52 PM,