Hello, Yes, I am actually working on this, and I proposed a first roadmap in a previous email:
https://lists.apache.org/thread.html/Zfq3cpnr55obgrs Notice that the first point is more on the scala/spark integration front, and we need two things, to use scio as an scala API/REPL for Beam (to be integrated as an official scala sdk soon, we hope). https://github.com/spotify/scio/ And to integrate the runtime artifacts of Beam, a good point is that we can base the work in the soon to be released version 0.1 of the Beam SDK/Runners, but I think we should focus on the spark runner as a first goal and eventually support all the other runners. I am more involved in the Beam side of the spectrum ( https://issues.apache.org/jira/browse/BEAM-290) than in the Zeppelin side, but I can help you with anything you need there, and I am interested into contributing into Zeppelin too, so we can work to make this progress. As a beginning point I just created a branch in my fork of Zeppelin so we can start working there if you agree. Don't hesitate to contribute or send me any link to any ongoing work from your part there. https://github.com/iemejia/incubator-zeppelin/tree/beam Regards, Ismael On Tue, May 31, 2016 at 7:39 PM, Minudika Malshan <minudika...@gmail.com> wrote: > Hi all, > > I was going to do this project for GSOC 2016. I submitted two proposals for > gsoc and the other proposal got accepted. > > However I'm more than happy to contribute for this project. > I would like to know if there's anyone already working on this > implementation. > > Thanks > Minudika >
