GitHub user kavinkumarks reopened a pull request:
https://github.com/apache/zeppelin/pull/1408
[ZEPPELIN-808] Changed Permissions on Notebooks do not provide helpful
error to user
### What is this PR for?
This is about showing information to the user when there are errors on
running paragraphs eg. there could be permission related issue with notebook.
### What type of PR is it?
Improvement
### Todos
NA
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-808
### How should this be tested?
* Create a notebook as a different user than the current user running the
zeppelin instance
* Try to run all the paragraphs or any individual paragraph for the notebook
* The information as shown in the screenshot should be displayed and the
dialog could be closed by the 'Close' button.
### 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-808-handle-notebook-permission-error
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1408.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 #1408
----
commit 99d99009feebfe71751beafecd88ce1c765f16cd
Author: Kavin <[email protected]>
Date: 2016-09-06T12:21:26Z
Show information to the user when there are errors with related to
permission on running paragraphs.
commit 308345e4796375a4e22044ec1b361e962664047d
Author: Kavin <[email protected]>
Date: 2016-09-12T14:55:49Z
Handle FileSystemException on running paragraph and show the relevant
error message to the user.
----
---
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.
---
