Hi Minudika, > Currently I am writing an interpreter for SiddhiQL which is a real time > complex event processing engine, as a part of research. > If you are interested, you can find the code at here. (It's too messy > though. Have a lot to clean up the in the code) > https://github.com/minudika/incubator-zeppelin
Thank you for sharing! That would be a huge plus for your proposal, but please remember that code quality would be an important factor on the proposal selection process, so please make sure that you have finished possible cleanups before attaching it to your application. On the side note - I can see your commits in master branch of your fork, why not to try the workflow Zeppelin uses <https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#source-control-workflow> [0] by tracking your work in different branches? From there it will be easy to submit a PR and ask other contributors for a code review, which could improve chances of getting high quality code at the end. > I would like to know the exact purpose of this project and expected outcome from the student. The purpose (the objective or the outcome or the goal) of this project is to have merged PR with a code + documentation + example of usage for a new Interpreter in Zeppelin, that works with Apache Beam SKD by the end of the summer. It might be bold goal, so in order to be reachable and get accepted it should be further divided on smaller goal aligned with GSoC timeline, and then even on a smaller "steps" on "how to get there". The expectations are that you will do this work, as part of your application proposal (with the help of potential mentors). In prev. email in this thread I posted some ideas on how those smaller goals can look like, but ultimately it's up to you to decide. So I would suggest you start looking into creating a proposal draft as early as possible. [5] Have some examples and docs from ASF on the proposal as well, so please make sure that you read it. Please also feel free to post it here to get the feedback from the community, and I will be happy to further assist you with it. Good proposal consists of: - list of high-level, measurable "results", or steps to archive the final objective\goal - laid out over the timeline (so expectations for "milestones" like mid-term are set) - each "result" with the further scope breakdown to a smaller action items (ideally, each not longer than 1day) - plus some background information, showing that you are qualified to do all that and put some thinking into details (links to your code here will help very much) > I am getting familiar with Apache beam nowadays. Please can you provide me some useful resources for that. [1], [2], [3], [4] are some resource to learn about Beam before it has finalized its move to Apache. Hope this helps! -- Alex 0. https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#source-control-workflow 1. https://cloud.google.com/dataflow/ 2. https://cloud.google.com/dataflow/what-is-google-cloud-dataflow 3. https://cloud.google.com/dataflow/blog/dataflow-beam-and-spark-comparison 4. https://github.com/GoogleCloudPlatform/DataflowJavaSDK-examples 5. https://community.apache.org/gsoc.html On Wed, Mar 2, 2016 at 2:50 AM, Minudika Malshan <minudika...@gmail.com> wrote: > Hi, > > First of all, thanks Alex for your reply. > Sorry for the delay. > Some thing has gone wrong with my mail thread. I just saw Alex's reply. > > I am getting familiar with Apache beam nowadays. Please can you provide me > some useful resources for that. > Beam developers said that it would take like a week to get the official > Apache documentation for beam done. > > Cheers, > Minudika > > Minudika Malshan > Undergraduate > Department of Computer Science and Engineering > University of Moratuwa. > > > > > On Sun, Feb 21, 2016 at 2:30 AM, Minudika Malshan <minudika...@gmail.com> > wrote: > > > Hi all, > > > > I am looking forward to contribute in this year GSOC. > > I have a basic understand in writing interpreters for zeppelin and have > > already implement an interpreter for WSO2 siddhi which is a complex event > > processing language. > > Could you please give me more details about the requirement for > > implementing a new interpreter for Apache beam? > > It would be a great help for me to getting familiar with this > > implementation. > > > > Thank you! > > > > Minudika Malshan > > Undergraduate > > Department of Computer Science and Engineering > > University of Moratuwa. > > > > > > > -- -- Kind regards, Alexander.
