Maziyar PANAHI created ZEPPELIN-3267:
----------------------------------------
Summary: Users are not authorised to restart Spark interpreter
Key: ZEPPELIN-3267
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3267
Project: Zeppelin
Issue Type: Improvement
Components: Interpreters, security
Affects Versions: 0.7.3
Environment: Apache Zeppelin 0.7.3
Apache Spark 2.2 CDH
YARN Cloudera 5.14
Reporter: Maziyar PANAHI
Following on this issue which was merged long time ago:
https://issues.apache.org/jira/browse/ZEPPELIN-987
I have two problems with this way of "securing" endpoints especially in
interpreters:
# If users are not supposed to access these 3 areas, shouldn't the UI be
smarter and hide them as well? Not really ergonomic to display a choice and
then say sorry you can't touch this.
# The bigger issue that I am just facing is users can't restart their Spark
interpreter after securing `/api/interpreter/**`. It says you are not
authorised to access /api/interpreters/settings/restart/xxxx.
It is really important for users to start a fresh Spark context since the
sessions are not terminated after some idle time (at least not in 0.7.3) like
Livy. So users may need to create a fresh Spark context/session and destroy old
variables/UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
