Re: Elastic Search Storage for Zeppelin Notebooks

[ashish rawat <dc...@gmail.com>]

Thanks Alexandra and Andrea.

I will create a Jira and start an initial discussion. Thanks for all the
help.

Regards,
Ashish

On Thu, Jun 30, 2016 at 3:02 PM, Alexander Bezzubov <bz...@apache.org> wrote:

> Hi Ashish,
>
> let's move this discussion to dev@ mailing list (by removing users@ from
> CC)
>
> As far as I understood, you are working on multiple things one being
> NotebookRepo implementation backed by Elasticsearch.
> That sounds great, and I would be happy to assist you with it and help by
> reviewing ideas\code as soon as you are ready to share those with the
> community here!
>
> Good place to start is - to create a separate JIRA issues for each of the
> changes you want to submit, attaching mocks\design idea before actual
> implementation. It's a good place to have technical discussion as well.
>
> From there please just submit at PR from you repo\branch, following
> project's contribution instructions [1].
> Feel free to \cc people in PR comments, so they get notified as soon as you
> think the code is ready for review (i.e my GH id is @bzz)
>
> We are always happy to bring new contributions to the project!
>
>  1. https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md
>
> --
> Alex
>
> On Thu, Jun 30, 2016 at 5:18 PM, Andrea Santurbano <sa...@gmail.com>
> wrote:
>
> > Hi Ashish,
> > if you share the github repo i would like to contribute!
> > Bests
> > Andrea
> >
> > Il giorno gio 30 giu 2016 alle ore 08:12 ashish rawat <
> dceashish@gmail.com>
> > ha scritto:
> >
> >> Hi,
> >>
> >> We have implemented a basic version of Elastic Search Storage for
> >> Zeppelin and would like to contribute it back to the main repo. But
> before
> >> we spend time in preparing a Pull Request, I just wanted to check
> >>
> >>    1. Does this feature make sense for the Zeppelin project and would be
> >>    accepted in main repo,
> >>    2. Would anyone be willing to review it, so that we can have an
> >>    initial discussion around how ready is our code for raising a Pull
> Request.
> >>
> >> We are also working on a couple of other features, including a read-only
> >> (Dashboard) mode, which would restrict updating params and output to
> >> notebook. It will be very helpful if someone can help us initially in
> >> making contributions to the project.
> >>
> >> Regards,
> >> Ashish
> >>
> >
>