> >>> What user see in notebook menu is still *My Project/My Spark
> > > Tutorial* *Note
> > > > >>> *which is no difference from what we see now.
> > > > >>>
> > > > >>> And thanks again for the feedback and comments, I am so glad to
up for discussion. My 2 cents below.
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> I am with Maksim and Felix on concerns with special characters now
> > > >>>> allowed in notebook names, and also concerns with different
> > charsets.
> > > >
gt;
> > >>>>
> > >>>>
> > >>>> But I’m still not comfortable with note ids in the name of the
> notebook
> > >>>> itself. Those names would look ugly if you shared your notebooks
> on github
> > >>>> for example. You don’t see J
the name of the notebook
> >>>> itself. Those names would look ugly if you shared your notebooks on
> >>>> github
> >>>> for example. You don’t see Jupyter notebooks with names like that. If
> >>>> you
> >>>> have to keep the note ids with t
I totally agree with the change. As I created an image for Zeppelin, it's
been painful store the notebooks in GitHub with a directory named with some
random hash and with the note.json in it. Having .zpln is even better
since I only need to store a file in the root of my repo and copy to the
right
he
>>>> note id at the top of the notebook as Ruslan suggested? Then you’d only
>>>> have to read the first line of each notebook.
>>>>
>>>>
>>>>
>>>> Presumably if you copied the notebooks to another Zeppelin server they
>>>&g
d the first line of each notebook.
>>>
>>>
>>>
>>> Presumably if you copied the notebooks to another Zeppelin server they
>>> would be restored with the same note ids there too? And hopefully there
>>> would be no id clash with notebooks a
on.
>
> The folder structure also sounds good.
>
>
>
> I'm afraid about non-latin symbols in folder and note name. And what about
> hieroglyphs?
>
>
>
> Apache Zeppelin may be the first to use Russian letters in file system in
> our company.
>
> I see a lo
ontent is json then why not use note_name.json
>>>instead of .zpln? That would make it easier for editors to know how to
>>> load/highlight the file contents.
>>>
>>>3. Is there any reason for not using *real* folders or directories
>>>for organis
ur company.
> I see a lot of risks to use non-latin symbols and a lot of issues to make
> new folder structure stable.
>
>
>
> --
> *От:* Jeff Zhang
> *Отправлено:* 13 августа 2018 г. 12:50
> *Кому:* users@zeppelin.apache.org
> *Тема
. 12:50
Кому: users@zeppelin.apache.org
Тема: Re: [DISCUSS] ZEPPELIN-2619. Save note in [Title].zpln instead of
[NOTEID]/note.json
>>> Do we need the note id in the file name at all? What’s wrong with just
>>> note_name.zpln?
The reason I keep note id is because currently we use
Ok, thanks Jeff – that all makes sense! Yes, rendering and diffing notebooks
in github would be very nice.
From: Jeff Zhang
Sent: 13 August 2018 10:50
To: users@zeppelin.apache.org
Subject: EXT: Re: [DISCUSS] ZEPPELIN-2619. Save note in [Title].zpln instead of
[NOTEID]/note.json
>>&
sers having characters in note name that are
> invalid for file name/file path?
>
>
>
>
> ----------
>
> *From:* Mohit Jaggi
> *Sent:* Sunday, August 12, 2018 6:02 PM
> *To:* users@zeppelin.apache.org
> *Cc:* dev
> *Subject:* Re: [DISCUSS]
to manually rename all the files/notebooks at present.
That’s not very user-friendly.
Thanks, Lucas.
From: Jeff Zhang
Sent: 13 August 2018 09:06
To: users@zeppelin.apache.org
Cc: dev
Subject: EXT: Re: [DISCUSS] ZEPPELIN-2619. Save note in [Title].zpln instead of
[NOTEID]/note.json
gust 12, 2018 6:02 PM
> *To:* users@zeppelin.apache.org
> *Cc:* dev
> *Subject:* Re: [DISCUSS] ZEPPELIN-2619. Save note in [Title].zpln instead
> of [NOTEID]/note.json
>
> sounds like a good idea!
>
> On Sun, Aug 12, 2018 at 5:34 PM Jeff Zhang wrote:
>
>> Motivation
Perhaps one concern is users having characters in note name that are invalid
for file name/file path?
From: Mohit Jaggi
Sent: Sunday, August 12, 2018 6:02 PM
To: users@zeppelin.apache.org
Cc: dev
Subject: Re: [DISCUSS] ZEPPELIN-2619. Save note in [Title].zpln
sounds like a good idea!
On Sun, Aug 12, 2018 at 5:34 PM Jeff Zhang wrote:
> Motivation
>
>The motivation of ZEPPELIN-2619 is to change the notes storage
> structure. Previously we store it using {noteId}/note.json, we’d like to
> change it into {note_name}_{note_id}.zpln. There are several
Motivation
The motivation of ZEPPELIN-2619 is to change the notes storage
structure. Previously we store it using {noteId}/note.json, we’d like to
change it into {note_name}_{note_id}.zpln. There are several reasons for
this change.
1.
{noteId}/note.json is not scalable. We put all
18 matches
Mail list logo
