Ok, I will remove the option section from both the get and the set rest api.
I will open a jira and pr with this mail embeded.
בתאריך יום ו׳, 28 באוג׳ 2015, 10:36 מאת moon soo Lee <m...@apache.org>:
> 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 <goi....@gmail.com> 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 <m...@apache.org>:
> >
> > > 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 <goi....@gmail.com> 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
> > > >
> > >
> >
>
