Lee moon soo created ZEPPELIN-2994:
--------------------------------------
Summary: Websocket/REST API to access ResourcePool
Key: ZEPPELIN-2994
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2994
Project: Zeppelin
Issue Type: New Feature
Reporter: Lee moon soo
h2. Motivation
[ResourcePool|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/ResourcePool.java]
is general purpose, distributed map across interpreter processes.
ResourcePool currently provides
* Put / Get any object
* List objects
* Invoke method of object in the ResourcePool
Because of ResourcePool is (logically) distributed across Interpreters,
interpreter can use it to communicate to other interpreters. Pass interpreter
result to other interpreter, let other interpreter call directly call one of
the method of SparkContext, etc.
h2. Websocket/REST API to ResourcePool
However, currently ResourcePool API is only accessible in Interpreter. If
front-end can have Websocket/Rest API to the ResourcePool, we'll have usages
like
* Interpreter store
[TableData|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/tabledata/TableData.java]
into the ResourcePool.
* Front-end read TableData directly from ResourcePool. (and visualize data)
This will open possibilities of
* Move pivot routine to the backend (because current pivot works in front-end
with partial data)
* Realtime visualization update on front-end as data changes
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
