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 ide
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
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 befo
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 i
Hi Ashish,
I think your approach is generally right.
It's bit annoying while type of paragraph.result varies.
I think 'angularObject' field is another field that you also need to take
care.
object inside 'angularObject' might also vary their types.
Another approach would be serialize part of / e
I could think of another hack. While saving, when paragraphs.result type is
string, move that to another field paragraphs.stringResult before saving to
elastic. And do the reverse when serving reading notes.
This might just work and looks relatively clean, but can there be more such
cases in Zeppe
Hi All,
I was trying to write an implementation of storage interface for elastic
search, so that notebooks can be highly available in a cluster. The
implementation of basic interface looked simple but I got stuck while
importing note.json data into elastic search. Unfortunately, the type of
paragr
