[
https://issues.apache.org/jira/browse/TOREE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153397#comment-15153397
]
Chip Senkbeil commented on TOREE-264:
-------------------------------------
Relevant to this would be [~nimbusgo] discussion of dynamic namespaces:
https://issues.apache.org/jira/browse/TOREE-157
My comments to sandboxing here:
https://issues.apache.org/jira/browse/TOREE-131?focusedCommentId=15104488&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15104488
Also, [~nimbusgo] code snippet and branch of sandboxed magics here:
https://issues.apache.org/jira/browse/TOREE-146?focusedCommentId=15104536&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15104536
I'll give it some thought and come back to you later.
> 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)