[
https://issues.apache.org/jira/browse/LIVY-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-666:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Support named interpreter groups
> --------------------------------
>
> Key: LIVY-666
> URL: https://issues.apache.org/jira/browse/LIVY-666
> Project: Livy
> Issue Type: New Feature
> Reporter: Naman Mishra
> Priority: Major
> Fix For: 0.10.0
>
> Attachments: multiple_interpreter_groups.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, a session can contain only one interpreter group. In order to
> support use case of multiple repls with the same spark application multiple
> interpreters with different variable scoping (something similar to scoped
> interpreter mode in Zeppelin:
> [https://zeppelin.apache.org/docs/0.8.0/usage/interpreter/interpreter_binding_mode.html#scoped-mode
>
> |https://zeppelin.apache.org/docs/0.8.0/usage/interpreter/interpreter_binding_mode.html#scoped-mode]),
> I propose to have "named interpreter groups", i.e., multiple interpreter
> groups in a session all sharing a spark context. The interpreter group can be
> specified on which the execution is supposed to happen in the execution API.
> Similar ask has been put in LIVY-325
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
