[jira] [Created] (ZEPPELIN-2494) API Display Type
Eric Charles created ZEPPELIN-2494: -- Summary: API Display Type Key: ZEPPELIN-2494 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2494 Project: Zeppelin Issue Type: New Feature Components: zeppelin-zengine Reporter: Eric Charles A recurring request goes around automation where users are willing to use the notebook in a scheduled tool. This means also that the output of the notes have to be processed by some software. To indicate an output to be processed by a tool, we should produced structured content, in other words JSON. The current output (DisplayType) are TEXT, HTML, TABLE... but nothing is forseen for JSON. I propose to add a type API (because %json is already taken by a spell, and anyway API better indicates the intent). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2359) Support Spell as Display
Eric Charles created ZEPPELIN-2359: -- Summary: Support Spell as Display Key: ZEPPELIN-2359 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2359 Project: Zeppelin Issue Type: Improvement Reporter: Eric Charles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2235) Helium load.js should reside in subfolder
Eric Charles created ZEPPELIN-2235: -- Summary: Helium load.js should reside in subfolder Key: ZEPPELIN-2235 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2235 Project: Zeppelin Issue Type: Improvement Environment: I had issue to enable some libraries (e.g. sigma.js) as Spell visualization. The solution that worked for me was to update HeliumBundleFactory.java and webpack.config.js so the load.js now resided in a subfolder (local-repo/helium-bundle/src/). The positive side-effect for me is also that the generation of the webpack is faster (maybe because the node_modules are not more scanned?). If this approach makes sense, I am happy to open a PR. Reporter: Eric Charles Assignee: Eric Charles -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-1395) Local or Remote Interpreter by Configuration
Eric Charles created ZEPPELIN-1395: -- Summary: Local or Remote Interpreter by Configuration Key: ZEPPELIN-1395 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1395 Project: Zeppelin Issue Type: Improvement Components: zeppelin-zengine Affects Versions: 0.6.2 Reporter: Eric Charles Assignee: Eric Charles Fix For: 0.6.2 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). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZEPPELIN-1354) Inject Services
Eric Charles created ZEPPELIN-1354: -- Summary: Inject Services Key: ZEPPELIN-1354 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1354 Project: Zeppelin Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Services like authentication, authorization, security filters... should be injected rather than manually instanciated. This will allow to give central + finer control and abstracting the functionaly in interface. For this, I propose to use Guice as injection framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZEPPELIN-903) Jersey2 instead of CXF for better JSON REST
Eric Charles created ZEPPELIN-903: - Summary: Jersey2 instead of CXF for better JSON REST Key: ZEPPELIN-903 URL: https://issues.apache.org/jira/browse/ZEPPELIN-903 Project: Zeppelin Issue Type: Improvement Reporter: Eric Charles -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZEPPELIN-902) Build can break with pyspark profile due to not accessible path
Eric Charles created ZEPPELIN-902: - Summary: Build can break with pyspark profile due to not accessible path Key: ZEPPELIN-902 URL: https://issues.apache.org/jira/browse/ZEPPELIN-902 Project: Zeppelin Issue Type: Improvement Reporter: Eric Charles Path for .spark-dist is outside the reactor. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 30.337 s [INFO] Finished at: 2016-05-30T15:34:30+02:00 [INFO] Final Memory: 73M/469M [INFO] [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.1:wget (download-pyspark-files) on project zeppelin-spark-dependencies: IO Error: Destination '/opt/zeppelin-master/spark-dependencies/target/../../.spark-dist/spark-1.6.1.tgz' directory cannot be created -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
