[ZEPPELIN-272] Remove option part from REST API

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.5.5
• Assignee: Eran W
• Reporter: Eran W
• Created: 30/Aug/15 06:05
• Updated: 05/Nov/15 14:54
• Resolved: 03/Sep/15 03:10

Description

Option part in setting is not longer used and blocked from the UI. it should be removed from the REST API as well.

attached in the mail thread about it.
I think 'remote' can be removed safely from REST API at least.
However, 'remote' ('option' as well) can not be removed simply from rest of
the system while there are codes depends on it.

'option' part was initially designed to store informations like 'ip
address', 'port number' of interpreter process, in case of they're not
running on the same machine.

Best,
moon

On Thu, Aug 27, 2015 at 11:57 PM IT CTO <[e-mail]> wrote:

> Shoul we remove the option part completely or just make remote read only
> and disregard value in the setter?
> It is importent to keep the json of the get match the json of the set.
> Eran
>
> בתאריך יום ו׳, 28 באוג׳ 2015, 09:51 מאת moon soo Lee <[e-mail]>:
>
> > I think It make sense to remove from REST API while UI is not supporting
> > it.
> > (the feature is still used in some tests)
> >
> > Thanks,
> > moon
> >
> >
> > On Thu, Aug 27, 2015 at 11:19 PM IT CTO <[e-mail]> wrote:
> >
> > > In the UI we don't support registering a local (does not use external
> > jvm)
> > > interperter setting but the REST API support it.
> > > Should we remove it? We want to create a stable API as possible
> > > Eran

Issue Links

• incorporates: ZEPPELIN-261 Interpreter REST API - create setting should return setting ID