GitHub user khalidhuseynov reopened a pull request:
https://github.com/apache/zeppelin/pull/2161
[ZEPPELIN-1697] Fix multiuser ws connection for secondary ZeppelinHubRepo
storage
### What is this PR for?
This is to fix problem with ws connection that was introduced in 0.7.0 with
`ZeppelinHubRepo` storage layer.
### What type of PR is it?
Bug Fix
### Todos
* [x] - fix multi-user ws connection issue
* [x] - handle back connection
* [x] - handle switch tokens
* [ ] - handle single token in conf
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1697
### How should this be tested?
TBD
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/khalidhuseynov/incubator-zeppelin
fix/ZEPPELIN-1697
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2161.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2161
----
commit a7ba1a00fa5d56bb978cb5d6c5e7f70da68d211e
Author: Khalid Huseynov <[email protected]>
Date: 2017-03-16T05:11:21Z
multi ws one way connection
commit 6525d0f28bc67ec685c15e998629c5c5e86d7463
Author: Khalid Huseynov <[email protected]>
Date: 2017-03-20T06:00:56Z
fix empty token case
commit 4c372257d6e698e37096be5946b073df1bd22acc
Author: Khalid Huseynov <[email protected]>
Date: 2017-03-20T08:41:18Z
fix ws back connection
commit 769ffb338482c37accb6a64256a46ed54e726b6f
Author: Khalid Huseynov <[email protected]>
Date: 2017-03-20T13:02:07Z
switch tokens routine
commit 48c7f8ba32a50b930ddc826a966a39c388feccdf
Author: Khalid Huseynov <[email protected]>
Date: 2017-03-20T13:04:22Z
handle empty tokens in rest handler
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
