Github user SachinJanani commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/955
@jongyoul There can be scenarios where user is starting RemoteInterpreter
embedded in his service by calling
`RemoteInterpreterServer server = new RemoteInterpreterServer(port)
server.start()`
So this changes will help user to specify the host and port on which
interpreter is executing and zeppelin will connect to that interpreter.This
changes will also be helpful when
ClusterManager(https://cwiki.apache.org/confluence/display/ZEPPELIN/Cluster+Manager+Proposal)
will be implemented.We are starting ZeppelinInterpreter on remote host along
with our service.
You are right that when we stop Zeppelin all interpreter will be stop but
it can be handled by overriding the RemoteInterpreterServer
---
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.
---
