Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/2974
I am guessing that would depend on whether we want to user to continue
doing other stuff or make them wait for the interpreter to start/restart.
The interpreter page is kind of a global config place. For scoped mode
interpreters or isolated mode or per note interpreters, each user/note could
have their own interpreter instance and so the interpreter page may not be the
best place to capture that. With %conf interpreter, now the admin could also
consider locking down the interpreter page in order to prevent global
interpreter restarts etc. With admin/user level settings locking down that page
would be more important. So user visible setting may be better off where they
are most applicable. On the notebook. What do you think? @felixcheung
@sameer79
---
