[ZEPPELIN-4300] expand configuration to allow for Jetty session cache file configuration

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: conf
• Assignee: Unassigned
• Reporter: Stu Thompson
• Created: 12/Aug/19 17:54
• Updated: 13/Aug/19 13:25

Description

Currently the built in Jetty session state in memory (a ConcurrentHashmap).  When Zeppelin is restarted the existing client browser sessions are lost, including the user's loggin state.

 

With a few simple changes to some java files (namely ZeppelinServer and ZeppelinConfiguration), Jetty can be configured and started with session persistence.

 

This arguably could be the default configuration, but probably shouldn't be.  (KISS.)