please help me understand the interpreter configuration process 1) When zeppelin first start it looks for interpreter.json in the conf dir 2) if found, uses that json for the configuration shown in the config menu. 3) if not found, ??? traverse the interpreter directory for all available interpreters? where does it get the default parameters from? 4) when user click Create+ button on the interpreter menu, the form shows a name and the interpreter combo-box is derived from the interpreter REST API that in turn gets its value from the interpreterFactory( https://github.com/apache/incubator-zeppelin/blob/12e5abf2803e4c5015998672b10642fc72aac0da/zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterFactory.java#L94) . *if no zeppelin-site.xml is present, where does the conf is taken from?*
5) current docs say we should add the new interpreter to the site.xml file - but all other interpreters are not in this file (actually only a template file is given with a fresh install) - I think docs should say something about "defaults interpreters which "ship" with zeppelin and other interpreters - or on the other hand this step is not needed? Thanks for the opportunity to take part in this project :-) Eran On Thu, Jul 9, 2015 at 6:36 PM Eran W (JIRA) <[email protected]> wrote: > Eran W created ZEPPELIN-163: > ------------------------------- > > Summary: Change Writing Zeppelin Interpreter documentation > page > Key: ZEPPELIN-163 > URL: https://issues.apache.org/jira/browse/ZEPPELIN-163 > Project: Zeppelin > Issue Type: Improvement > Reporter: Eran W > Priority: Minor > > > 1) change wording on What is Zeppelin Interpreter > Interpreter can be launched either using separate JVM process or separate > classloader. The defualt is using separate JVM process (by checking 'fork' > in Interpreter menu). When Interpreter is running in separate JVM process, > it's communicating with Zeppelin via thrift. The other option is to use > separate classloader, note that somtime separate classloader can causes > problem especially when your interpreter uses reflections or trying to grab > standard out/err. > > 2) Add to Configure your interpreter > What do we need to do for the interpreter to show up in the interpreter > menu... > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
