On Mon, Oct 24, 2016 at 12:52 PM, Ismaël Mejía <[email protected]> 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.
>

Note that we recently added a list of current features branches (and their
jira components) here:
http://beam.incubator.apache.org/contribute/work-in-progress/

I agree it would be great to hear how each of them are progressing!


>
> 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/


That doc for the capability matrix was only used while we figured out the
initial data -- it's been fully replaced by the link you have. (Generally
information is moved to the website once it stabilizes.)

Adding information to this page is currently part of the requirements for
moving to the master branch:
http://beam.incubator.apache.org/contribute/contribution-guide/#merging-into-master


It'd be great to have this information available somewhere for each runner
on a feature branch too -- both what's currently supported and what is
expected to be supported before merging.


>
> 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.

​
>

Reply via email to