[ https://issues.apache.org/jira/browse/LIVY-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932134#comment-16932134 ]
Naman Mishra commented on LIVY-666: ----------------------------------- [~jerryshao] Thanks for reviewing the plan. As mentioned above, statement related APIs will need to be slightly changed as follows. Will keep the APIs backward compatible. * Statement creation (POST <session-id>/statements)[Must have]: Optional parameter "interpreterGroup" to specify the context of execution of this statement. If unspecified, we can default to a "default" interpreter group. Backward compatibility is maintained with the default context. * Statement retrieval (GET <session-id>/statements or /statement/<id>)[Nice to have]: Additional attribute "interpreterGroup" in response to identify the execution context of statement. This should be backward compatible as well. * Listing of interpreter groups [Nice to have]: Implement new API to list all existing interpreter groups under a session to help with debugging purposes. > 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 > Attachments: multiple_interpreter_groups.png > > > 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.3.4#803005)