Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Zeppelin's initialization steps for interpreters was to help users to use Zeppelin easily. At the early stage, it helps to initialize all things from interpreters directly because much of the settings have been changed for every release and users confused which is the most proper setting to use interpreters. Zeppelin server code was also written to support this situation and it makes code complicated. But recently, there weren't many changes for each release and it means we don't have to initialize all settings from interpreters directly. We can provide a pre-created interpreter.json for first-time users and don't have to override automatically because we wouldn't change much with every release.
I suggest that we can simplify our logic for InterpreterSettingManager by removing some initialization logic.