[jira] [Updated] (TOREE-268) Plugin System

["Chip Senkbeil (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TOREE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chip Senkbeil updated TOREE-268:
--------------------------------
    Description: 
https://github.com/apache/incubator-toree/pull/8

Currently, we do not have a robust system for others to extend the Toree kernel. The only extensible component is magics, which allow you to add unique functions to the kernel that have access to various dependencies.

A plugin system will enable us to do the following:
# Enable users to provide code that executed when the kernel is started
# Enable users to tap into Akka messages such as code execution, code completion, and more to produce side effects
# Clean up our bootstrapping code, which has a specific ordering of dependency creation (can be moved to separate classes)
# More easily extend dependencies available to magics (currently have trait per dependency and a dependency map class with a method per dependency)
# Provide internal access to dynamic events like SparkListener
# Add comm initialization code (thanks to #1) without needing to send a code execution request from the client
# Better standardize adding new interpreters (currently we have hard-coded logic to support our four interpreters)
# Extend the actor system with new actors through plugins
# Provide alternative frontends other than ZeroMQ

  was:
https://github.com/apache/incubator-toree/pull/8

Currently, we do not have a robust system for others to extend the Toree kernel. The only extensible component is magics, which allow you to add unique functions to the kernel that have access to various dependencies.

A plugin system will enable us to do the following:
# Enable users to provide code that executed when the kernel is started
# Enable users to tap into Akka messages such as code execution, code completion, and more to produce side effects
# Clean up our bootstrapping code, which has a specific ordering of dependency creation (can be moved to separate classes)
# More easily extend dependencies available to magics (currently have trait per dependency and a dependency map class with a method per dependency)
# Provide internal access to dynamic events like SparkListener
# Add comm initialization code (thanks to #1) without needing to send a code execution request from the client
# Better standardize adding new interpreters (currently we have hard-coded logic to support our four interpreters)


> Plugin System
> -------------
>
>                 Key: TOREE-268
>                 URL: https://issues.apache.org/jira/browse/TOREE-268
>             Project: TOREE
>          Issue Type: New Feature
>            Reporter: Chip Senkbeil
>            Assignee: Chip Senkbeil
>
> https://github.com/apache/incubator-toree/pull/8
> Currently, we do not have a robust system for others to extend the Toree kernel. The only extensible component is magics, which allow you to add unique functions to the kernel that have access to various dependencies.
> A plugin system will enable us to do the following:
> # Enable users to provide code that executed when the kernel is started
> # Enable users to tap into Akka messages such as code execution, code completion, and more to produce side effects
> # Clean up our bootstrapping code, which has a specific ordering of dependency creation (can be moved to separate classes)
> # More easily extend dependencies available to magics (currently have trait per dependency and a dependency map class with a method per dependency)
> # Provide internal access to dynamic events like SparkListener
> # Add comm initialization code (thanks to #1) without needing to send a code execution request from the client
> # Better standardize adding new interpreters (currently we have hard-coded logic to support our four interpreters)
> # Extend the actor system with new actors through plugins
> # Provide alternative frontends other than ZeroMQ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)