[
https://issues.apache.org/jira/browse/TOREE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153618#comment-15153618
]
Chip Senkbeil commented on TOREE-264:
-------------------------------------
The REPL generates a package name here:
https://github.com/apache/spark/blob/master/repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkIMain.scala#L1007
Which in turn comes from the object here:
https://github.com/apache/spark/blob/master/repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkIMain.scala#L985
The second link has a comment about the session names coming from system
properties, but I don't know what system properties. Obviously, if we can
change those session names, then we should be okay.
> Support multiple sessions in the kernel each with their own isolated
> interpreters
> ---------------------------------------------------------------------------------
>
> Key: TOREE-264
> URL: https://issues.apache.org/jira/browse/TOREE-264
> Project: TOREE
> Issue Type: Improvement
> Reporter: Gino Bustelo
>
> Many folks are very interested in having multiple users connecting to one
> Kernel/Toree process and sharing the same SparkContext.
> I've always considered us already supporting thins use-case, but with the
> caveat that all users also share the same interpreter and can lead to lots of
> race-conditions.
> I'm thinking that we could more sanely support multiple users by routing them
> to isolated interpreters that share the SparkContext but have independent
> variable namespace.
> Thoughs?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
