[
https://issues.apache.org/jira/browse/SPARK-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033302#comment-15033302
]
Sree Vaddi commented on SPARK-4605:
-----------------------------------
After going through the discussion on the proposal and the referred links in
it; in my opinion, it benefits to combine apache zeppelin with
spark-kernel(torii, renamed in incubation proposal). This saves a lot of
effort on 'torii' and up-brings the zeppelin. Most important, the users gets
benefit from two projects in one.
> Proposed Contribution: Spark Kernel to enable interactive Spark applications
> ----------------------------------------------------------------------------
>
> Key: SPARK-4605
> URL: https://issues.apache.org/jira/browse/SPARK-4605
> Project: Spark
> Issue Type: New Feature
> Reporter: Chip Senkbeil
> Attachments: Kernel Architecture Widescreen.pdf, Kernel
> Architecture.pdf
>
>
> Project available on Github: https://github.com/ibm-et/spark-kernel
> ----
> This architecture is describing running kernel code that was demonstrated at
> the StrataConf in Barcelona, Spain.
> ----
> Enables applications to interact with a Spark cluster using Scala in several
> ways:
> * Defining and running core Spark Tasks
> * Collecting results from a cluster without needing to write to external data
> store
> ** Ability to stream results using well-defined protocol
> * Arbitrary Scala code definition and execution (without submitting
> heavy-weight jars)
> Applications can be hosted and managed separate from the Spark cluster using
> the kernel as a proxy to communicate requests.
> The Spark Kernel implements the server side of the IPython Kernel protocol,
> the rising “de-facto” protocol for language (Python, Haskell, etc.) execution.
> Inherits a suite of industry adopted clients such as the IPython Notebook.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
