You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "Stu Thompson (JIRA)" <ji...@apache.org> on 2019/08/12 17:55:00 UTC

[jira] [Created] (ZEPPELIN-4300) expand configuration to allow for Jetty session cache file configuration

Stu Thompson created ZEPPELIN-4300:
--------------------------------------

             Summary: expand configuration to allow for Jetty session cache file configuration
                 Key: ZEPPELIN-4300
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4300
             Project: Zeppelin
          Issue Type: Improvement
          Components: conf
            Reporter: Stu Thompson


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.)

 

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)