GitHub user kavinkumarks reopened a pull request:

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

    [ZEPPELIN-1142] Zeppelin allows two users to simultaneously edit the 
notebook permissions

    ### What is this PR for?
    This is about storing the owner information on creating a note so when the 
same user tries to edit the permissions of the note he could do it successfully.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    NA
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1142
    
    ### How should this be tested?
    Check the below cases via the web application or REST API calls and the 
owner information should be persisted properly.
    * Create note
    * Clone note
    * Import note
    
    ### 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/kavinkumarks/zeppelin 
zeppelin-1142-simultaneous-note-permission-error

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

    https://github.com/apache/zeppelin/pull/1393.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 #1393
    
----
commit 4412692cdd48a23ccf9578ddbcfe0205784ac92d
Author: Kavin <kavin.ku...@imaginea.com>
Date:   2016-09-01T11:19:41Z

    Store owner information on creating a note and added integration test
    cases for the relevant scenarios.

commit 85af4e6178c82414526386ac3d72239a279789b4
Author: Kavin <kavin.ku...@imaginea.com>
Date:   2016-09-06T09:20:14Z

    Removed the duplicate instance of notebook variable and reused the
    existing one.

----


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