[jira] [Created] (ZEPPELIN-3197) Dynamic Interpreter Loading/Unloading results in 404

2018-01-31 Thread Simeon H.K. Fitch (JIRA)
Simeon H.K. Fitch created ZEPPELIN-3197:
---

 Summary: Dynamic Interpreter Loading/Unloading results in 404
 Key: ZEPPELIN-3197
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3197
 Project: Zeppelin
  Issue Type: Bug
  Components: documentation, Interpreters, zeppelin-interpreter, 
zeppelin-server
Affects Versions: 0.7.3
Reporter: Simeon H.K. Fitch


According to the documentation, one should be able to dynamically load and 
unload Zeppelin interpreters at runtime:

http://zeppelin.apache.org/docs/0.7.3/manual/dynamicinterpreterload.html

However, going to the `/api/interpreter/load/` and `/api/interpreter/unload/` 
REST endpoints results in a 404 HTTP response.

Looking through the source, I'm unable to find where the `load` and `unload` 
endpoints might be handled. Therefore, either a) the docs or incorrect, or b) 
the feature isn't working.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (ZEPPELIN-2556) NPE in HeliumVisualizationFactory

2017-05-16 Thread Simeon H.K. Fitch (JIRA)
Simeon H.K. Fitch created ZEPPELIN-2556:
---

 Summary: NPE in HeliumVisualizationFactory
 Key: ZEPPELIN-2556
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2556
 Project: Zeppelin
  Issue Type: Bug
  Components: helium
Affects Versions: 0.7.0
 Environment: Docker image `dylanmei/zeppelin:0.7.0`
Reporter: Simeon H.K. Fitch


Not sure what's causing it. Zeppelin runs fine except for no entries in the 
Helium page.

```
java.lang.NullPointerException: null
at 
org.apache.zeppelin.helium.HeliumVisualizationFactory.bundle(HeliumVisualizationFactory.java:230)
at 
org.apache.zeppelin.helium.HeliumVisualizationFactory.bundle(HeliumVisualizationFactory.java:98)
at 
org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:129)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createSingletonInstance(CXFNonSpringJaxrsServlet.java:382)
at 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createApplicationInstance(CXFNonSpringJaxrsServlet.java:454)
at 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createServerFromApplication(CXFNonSpringJaxrsServlet.java:432)
at 
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.init(CXFNonSpringJaxrsServlet.java:93)
at 
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:616)
at 
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396)
at 
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871)
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
at 
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at 
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:163)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
```




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (ZEPPELIN-2264) DevInterpreter settings references JDBC driver.

2017-03-15 Thread Simeon H.K. Fitch (JIRA)
Simeon H.K. Fitch created ZEPPELIN-2264:
---

 Summary: DevInterpreter settings references JDBC driver.
 Key: ZEPPELIN-2264
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2264
 Project: Zeppelin
  Issue Type: Task
  Components: helium
Affects Versions: 0.7.0
Reporter: Simeon H.K. Fitch
Priority: Minor


In the code for the dev interpreter, [this 
file](https://github.com/apache/zeppelin/blob/master/helium-dev/src/main/resources/interpreter-setting.json)
 references a JDBC driver under the `port` property. There doesn't seem to be 
any JDBC code in the dev interpreter. Is this a copy/paste accident? It's 
certainly confusing when trying to use the DevInterpreter for the first time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)