Ahyoung Ryu created ZEPPELIN-1973:
-------------------------------------
Summary: List all available Helium packages under
zeppelin.apache.org
Key: ZEPPELIN-1973
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1973
Project: Zeppelin
Issue Type: Sub-task
Reporter: Ahyoung Ryu
Assignee: Ahyoung Ryu
*Overview*
After #1842 merged, we can load Helium packages placed under local helium repo
(ZEPPELIN_HOME/helium) and enable/disable them via Zeppelin GUI. Additionally
anyone can create his/her own “VISUALIZATION” pkg as described in [Writing a
new
Visualization|https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/development/writingzeppelinvisualization.html]
and publish it to npm registry. So it’ll be nice if we can see all available
Zeppelin visualization pkg list and select to use other ppl's.
*Where?*
The place can be [zeppelin.apache.org|https://zeppelin.apache.org] to provide
this info.
*How?*
To do this, we can retrieve npm pkgs only having `zeppelin-vis` as dependency,
download and save somewhere as central repo. So I would suggest to using AWS
Lambda for fetching registered Helium pkg info periodically and probably also
we need to convert npm’s package.json -> helium-application.json. Then this
changed json files can be saved S3.This S3 storage can be used for Helium
default repo in the near future. (Currently user needs to create
ZEPPELIN_HOME/helium local repo and place the helium json files manually.) Then
as long as the pkg published in npm registry the all available VISUALIZATION
type of pkgs can be listed in Zeppelin GUI as well.
*Other issue*
But to use AWS service, surely we need an account. So for the continous
managing, I’d suggest most of Zeppelin PMC’s account like Spark tutorial
bank.csv file does. (_Whenever we can change this if it can be a problem_)
tl;dr please see the attached image :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
