[GitHub] zeppelin issue #1390: [WIP] [ZEPPELIN-1339] [ZEPPELIN-1000] Note and service...

[echarles]

Github user echarles commented on the issue:

    https://github.com/apache/zeppelin/pull/1390
  
    @khalidhuseynov Good to discuss with you about what a multiuser note 
management would be.
    
    For the file system repo, this PR will give you:
    
    ```
    ├── anonynmous
    │   ├── 2A94M5J1Z
    │   │   └── note.json
    │   ├── 2BQA35CJZ
    │   │   └── note.json
    │   ├── r
    │   │   └── note.json
    │   └── interpreter-setting.json
    ├── user1
    │   ├── 2BWADFP17
    │   │   └── note.json
    │   └── interpreter-setting.json
    └── user2
        ├── 2BU5DAHBJ
        │   └── note.json
        └── interpreter-setting.json
    ```
    
    The note folders are moved one level-down, each user having its workspace.
    
    Each user also has its own `interpreter-setting.json` (was before in the 
`conf` folder) - Just like before, each interpreter contribute to the settings 
via classpath or file system.
    
    Interpreter settings and bindings assignment is made possible by keeping 
separate interpreterfactory, searchservice... per web user session.
    
    To ensure backwards compatibility, I propose (not yet implemented) a 
`zeppelin.notes.per-user` configuration being `false` by default.
    
    The other repository implements (azure, github...) need more love with the 
credential service (each user can have their own credentials).
    
    PS: I had a quick look at #1392 - Let's continue this discussion - 
Depending on the outcomes, we can decide `what`, `who` and `where` - About the 
`when`, the soone the better.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---