Very Exciting! The Go language is in a very different point of the design space than either Java or Python; it's interesting to see how you've explored making this fit with the Beam model. Thanks for the detailed design doc.
+1 to targeting the portability framework directly. Once all runners are upgraded to use this too it'll just work everywhere. On Thu, Nov 30, 2017 at 8:51 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Henning, > > Thanks for the update, that's great ! > > Regards > JB > > On 12/01/2017 12:40 AM, Henning Rohde wrote: >> >> Hi everyone, >> >> We have been prototyping a Go SDK for Beam for some time and have >> reached a point, where we think this effort might be of interest to the >> wider Beam community and would benefit from being developed in a proper >> feature branch. We have prepared a PR to that end: >> >> https://github.com/apache/beam/pull/4200 >> >> Please note that the prototype supports batch only, for now, and includes >> various examples that run on the Go direct runner. Go would be the first SDK >> targeting the portability framework exclusively and our plan is to extend >> and benefit from that ecosystem. >> >> We have also prepared an RFC document with the initial design, motivations >> and tradeoffs made: >> >> https://s.apache.org/beam-go-sdk-design-rfc >> <https://s.apache.org/beam-go-sdk-design-rfc> >> >> The challenge is that Go is quite a tricky language for Beam due to >> various limitations, notably strong typing w/o generics, and so the >> approaches taken by Java and Python do not readily apply. >> >> Of course, neither the prototype nor the design are in any way final -- >> there are many open questions and we absolutely welcome ideas and >> contributions. Please let us know if you have any comments or objections (or >> would like to help!). >> >> Thanks, >> Henning Rohde, Bill Neubauer, and Robert Burke > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
