Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/413#issuecomment-188563134
Thank you @bzz for organizing the check list very well.
Overall concept and approach of this PR make sense a lot.
How about think little bit more before we move on?
Implementation side, I'd like to generalize little bit more and align more
with other components that already exists or planned in the future.
I think it make sense to introduce some common data type (like RDD in
Spark) for the Zeppelin, the common data type abstracts underlaying physical
data. In addition to current InterpreterResult.
And this common data type can be exported to
[ResourcePool](https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/resource/ResourcePool.java)
from any interpreter.
And then we can create proxy object of this common data type in Zeppelin
server side, so Zeppelin server can bring data from interpreter process.
This data can be provided by REST API or any other API.
So basically approach is the same but little bit more generalized and use
existing component.
---
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.
---
