GitHub user khalidhuseynov reopened a pull request:

    https://github.com/apache/zeppelin/pull/1392

    [ZEPPELIN-1437] Multi-user note management - user aware reload broadcast

    ### What is this PR for?
    This PR addresses part of multi-user note management in Zeppelin. One of 
the tasks namely listing notes per user on Zeppelin start was addressed in 
#1330. However that PR didn't solve all problems, and reloading notes was 
incomplete as well as socket broadcast was not user aware 
[ZEPPELIN-1437](https://issues.apache.org/jira/browse/ZEPPELIN-1437). This PR 
addresses that issue.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [x] - list notes per user on reload
    * [x] - broadcast per user (multicast)
    * [x] - tests
    * [x] - use authorization module to filter notes on sync
    * [ ] - discussion and review
    
    ### What is the Jira issue?
    [Zeppelin-1437](https://issues.apache.org/jira/browse/ZEPPELIN-1437)
    
    ### How should this be tested?
    change some note permissions and should see different view for different 
users
    
    ### Screenshots (if appropriate)
    
![reload_broadcast](https://cloud.githubusercontent.com/assets/1642088/18679507/e4a0161c-7f9a-11e6-9d57-0930abf4b780.gif)
    
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? yes
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/khalidhuseynov/incubator-zeppelin 
feat/multi-user-notes

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1392.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 #1392
    
----

----


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

Reply via email to