GitHub user echarles opened a pull request:
https://github.com/apache/zeppelin/pull/1390
[WIP] [ZEPPELIN-1339] [ZEPPELIN-1000] Note and services per user
### What is this PR for?
This implements "notes per user" and "Multiple-users on a single WEB
server" - For implementation reasons (the static fields present on the zeppelin
server, and the need for each users to bind/configure their own note to the
interpereters managed by the InterpreterFactory), this PR implements both - In
other words, it would have been too difficult to decouple both).
### What type of PR is it?
[Feature]
### Todos
* [ ] - More test
* [ ] - Documentation
* [ ] - Migration (notebook folder structure changes)
* [ ] - Discuss the S3, Azure... repo cases
* [ ] - Check unit tests
* [ ] - Forsee a "shared" notebook workspace to mimick current behavior
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1339
* https://issues.apache.org/jira/browse/ZEPPELIN-1000
### How should this be tested?
Logon / Logout with different users and check that the notes are different.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? N
* Is there breaking changes for older versions? Y
* Does this needs documentation? Y
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/datalayer/zeppelin-datalayer multiuser
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1390.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 #1390
----
commit 60c9380c3545e294ae8e776275b628899738cfc1
Author: Eric Charles <[email protected]>
Date: 2016-08-31T15:43:09Z
WIP Initial working implementation
----
---
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.
---
