ailto:felixcheun...@hotmail.com]
> *Sent:* Wednesday, September 14, 2016 6:24 AM
> *To:* users@zeppelin.apache.org; users@zeppelin.apache.org
>
>
> *Subject:* Re: Hbase configuration storage without data
>
>
>
> I like that approach - though you should be able to clear result o
umar
From: Felix Cheung [mailto:felixcheun...@hotmail.com]
Sent: Wednesday, September 14, 2016 6:24 AM
To: users@zeppelin.apache.org; users@zeppelin.apache.org
Subject: Re: Hbase configuration storage without data
I like that approach - though you should be able to clear result output before
expor
gt;>
Sent: Monday, September 12, 2016 10:38 AM
Subject: Re: Hbase configuration storage without data
To: <users@zeppelin.apache.org<mailto:users@zeppelin.apache.org>>
one option is to keep the data in separate files. notes.json can contain the
code and the data can be a pointer to /pat
>
> *Vikash Kumar*
>
> *From:* moon soo Lee [mailto:m...@apache.org]
> *Sent:* Wednesday, September 7, 2016 8:39 PM
> *To:* users@zeppelin.apache.org
> *Subject:* Re: Hbase configuration storage without data
>
>
>
> Hi,
>
>
>
> For now, code and result dat
Hi,
For now, code and result data are mixed in note.json, which is represented
by 'class Note' [1]. And every Notebook storage layer need to implement
'NotebookRepo.get()' [2] to read note.json from underlying storage and
convert it into 'class Note'.
As you see the related API and class
Hi all,
We are storing the note.json configuration into hbase as it is
stored into File system. As default behavior in note.json the query data is
stored along with configuration. But we want to store the configurations only
and when user loading its note then query should get
