GitHub user echarles opened a pull request:
https://github.com/apache/zeppelin/pull/1385
[ZEPPELIN-1395] Local or Remote Interpreter by Configuration
### What is this PR for?
The current remote interpreter (launched via shell) is scalable and open
but suffers from 2 limitations:
- It does not allow to easily debug in the IDE.
- It does not allow to embedd Zeppelin (for small deployements) in a single
jar.
A configuration per interpreter "Remote Interpreter" (true/false, true by
default) is proposed.
An additional property `zeppeline.interpreter.remote' in zeppelin-site.xml
is also proposed (a new interpreter will be created with that value for it
`option.remote` attribute).
### What type of PR is it?
[Improvement]
### Todos
* [ ] - Value defined in zeppelin-site.xml is not honored when creating a
new interepreter
* [ ] - Unit Test
* [ ] - Documentatoin
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1395
### How should this be tested?
Load Zeppelin source in your IDE and start ZeppelinServer in debug mode
Put breakpoints in the interpreter sources, Set / Uset the "Remote
Interpeter (see screeenshot).
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? N
* Is there breaking changes for older versions? N
* Does this needs documentation? Y
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/datalayer/zeppelin-datalayer
remote-interpreter-config
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1385.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1385
----
commit f70331d28eb84158e05493ab5e989b37781dbc2b
Author: Eric Charles <[email protected]>
Date: 2016-08-30T03:48:52Z
initial working implementation of local/remote interpreter configuration
----
---
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.
---
