Github user eranwitkon commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/334#issuecomment-146074254
I agree that we shouldn't expose just random API but these are not just any
utility functions, this is working with notebooks from external
applications. To me, it can be benificial in few use cases such as one
described.
Creating notebooks is zeppelin core functionally and will foster the use of
Zepplin but exposing interperter is something I wouldn't expose.
Last but not least, these services are available today as socket API...
Hope this clearify things, as you see I am a strong believer for API ð
Eran
×ת×ר×× ××× ×׳, 7 ×××ק׳ 2015, 05:07 ××ת CORNEAU Damien <
notificati...@github.com>:
> Does the Rest API also have the Allow-Origins restrictions?
>
> I got nothing against making more REST API calls, however those calls has
> to have a benefit for Zeppelin. In the last case of @vmakhaev
> <https://github.com/vmakhaev> it is pretty much out of Zeppelin context.
>
> If the context is to have some kind of development kit/Public Rest API
> (Allow outside process to use the Zeppelin Server), and it's in the
> RoadMap, then we can work on that. However I don't think random REST API
> calls without real applications or goal in Zeppelin context should be
> included in the main source code.
>
> â
> Reply to this email directly or view it on GitHub
>
<https://github.com/apache/incubator-zeppelin/pull/334#issuecomment-146057741>
> .
>
--
Eran | "You don't need eyes to see, you need vision" (Faithless)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
