Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/835#issuecomment-210727637
Thanks @jongyoul for taking care of the issue.
I think this subject is related to
[ZEPPELIN-598](https://issues.apache.org/jira/browse/ZEPPELIN-598) and
[ZEPPELIN-533](https://issues.apache.org/jira/browse/ZEPPELIN-533).
ZEPPELIN-598 try to load interpreter dynamically, from maven repository.
and ZEPPELIN-533 will create registry for that (as well as registry for
helium applications, notebook repo)
Considering ZEPPELIN-598 and ZEPPELIN-533, i think source of interpreter
information need to be packaged and distributed with interpreter, rather than
placed in `interpreter-setting.json` all together.
For example Helium Application, each application provides separate json
file that keeps [informations of
application](https://github.com/Leemoonsoo/incubator-zeppelin/blob/ZEPPELIN-732-up/zeppelin-examples/zeppelin-example-wordcloud/zeppelin.wordcloud.json),
to helium package registry.
I was thinking the same deploy model for Interpreter and NotebookRepo.
Deploy,
1) Deploy jar into maven repository.
2) Deploy json file that contains information into Helium registry. (either
local or central (future)).
Use,
1) Zeppelin fetches all json file from Helium registry to list available
Interpreters/NotebookRepo/Application
2) Zeppelin dynamically loads jar when user selects from maven repository
and run it based on information from helium registry.
What do you think?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
